[rami-hatoum]

What this changes

An agent with many tools at hand, asked to create a playbook, wrote a document with its documents tool and never called this server. The server's instructions opened by saying what a playbook is, and the playbook tools said "use it when the person wants a new playbook", but nothing said that such a request, in whatever words, is a request for this server.

The instructions open with the claim, in words that fit any line of business. "Whatever the person wants done that should keep working after this conversation, however they put it and in any line of business, is a playbook on this server, not a document, a plan, a note or a one-off answer. Auto Runtime makes and runs playbooks; Studio manages them; your agent is a separate client." Then what a playbook holds, as before. The OpenAPI document's description opens the same way.

Three sentences leave the instructions, so that a connection's instructions stay within the 2,000 characters a client shows: that a run of a workflow answers started and get_run shows how it ended, which run_definition says; the build clause of the prediction sentence, which the prediction guide says; and how a reasoning function names its model and tools, which list_models, search and the reasoning guide say. With every tool, the instructions take 1,987 characters on /mcp and on the org endpoint and 1,575 on a playbook's.

The playbook tools claim it too. create_playbook starts with "Start here when the person wants something done in their business that should keep working after this conversation, however they put it, and none of their playbooks covers it." list_playbooks starts with "Use it when the person speaks of their playbooks, or wants something done that one of them may cover." Each drops the clause that repeated it. The org endpoint's listing grows to 13,155 bytes, so its bound moves to 13,200, the least hundred that holds it, as the api README records.

Tests

• The instructions of each endpoint open with the claim, their lengths are pinned, and the bound's check holds at 2,000 and 2,001 characters.
• The two tools' descriptions and the listings' sizes, as the MCP listing and the OpenAPI document serve them.

Checklist

• The PR title is a conventional commit with a workspace scope, such as feat(reasoning): .... It becomes the squash commit and the changelog entry.
• pnpm check passes locally, with every file at 100% coverage.
• I've signed the Contributor License Agreement (the CLA bot asks on your first PR).