Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only/idempotent/no-destruction, so the description's added value is the auth prerequisite ('linked account (transport auth)'), the payload-vs-file distinction, and the 'no second unsolicited reply' note that tells the agent not to wait for a follow-up. It stops short of describing pagination termination or the cursor lifecycle beyond the next.arguments hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome, then mode selection, then the scaffold-continuation case, then the auth caveat. Dense and largely waste-free, though the accumulation of parenthetical asides ('default: all', 'transport auth') slightly taxes readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of the return shape and does so ('JSON bodies + destination paths'), plus auth and the incomplete-result continuation path. Minor gaps remain on what a cursor-terminated or error response looks like, but an agent has enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics the schema doesn't: field's default of all, the list-vs-name fetch modes, and the mapping of cursor to next.arguments from a prior incomplete scaffold result. That linkage is the kind of meaning the schema alone cannot convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns ... this account's named site profiles') and immediately scopes what it is not ('not as files in a template repo'), which separates it from get_scaffold/purchase_scaffold. The enumerated categories (privacy, terms, cookies, licence, custom_field) sharpen the resource further.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode selection ('Pass list: true to see profile names, or siteprofilename to fetch one') and cross-tool routing: on an incomplete purchase_scaffold/get_scaffold result, call this with next.arguments. An agent can pick the right call path without inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.