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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds substantive behavior: turbopress injects title/description into the homepage on every preview/publish, subpages without their own title inherit it, an empty string removes the value, and apply_now immediately forks a new version from the live site. These are non-obvious side effects the agent needs.

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-loads the read/set purpose, then layers side effects and the apply_now/publish workflow. Dense but each clause carries needed information; slightly long, but no filler sentences.

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?

For a mutating tool with no output schema, it covers the read-mode return, write side effects, character guidance, empty-string semantics, and the multi-step apply_now → deploy_publish workflow. Nothing an agent needs to invoke it safely is missing.

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 baseline is 3, but the description adds meaning beyond the schema: SEO-recommended lengths (title ≤60, description ≤160 vs the schema's 120/320 maxima), the empty-string-removes-value convention, and the preview/deploy semantics of apply_now. It does not explain why the schema allows longer than the recommended lengths, a minor gap.

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+resource: reads or sets the site title and description (the Google snippet) for a turbopress AI Launch site. It is clearly distinguishable from generic siblings like update_wordpress_core or set_contact_form by naming the exact fields and their external effect.

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?

Explicitly gives the read path (no title/description → return current values) and the write path, plus the apply_now workflow: create a preview, show it to the user, and only call deploy_publish with the returned deploy_id after explicit consent. This names the alternative tool and the condition that selects it.

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