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

With no annotations, the description carries the full disclosure burden. It usefully discloses that the rewrite is asynchronous, does not publish, and requires a follow-up list_content_drafts call, but it does not describe permissions, error behavior, or what the immediate response contains.

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?

The core behavior and follow-up step are front-loaded and easy to scan. There is minor waste from repeating the title and including boilerplate HTTP 200 response text, but the useful content is not buried.

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?

Given no output schema and no annotations, the description provides enough context to call the tool correctly: what it does, how to obtain the handle, examples for the instruction, and how to retrieve the resulting text. It leaves some operational details undocumented, but the async workflow is covered.

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 description coverage is 0%, so the description has to compensate. It does so for both parameters by explaining that handle is a ctnt_ handle from list_content_drafts and giving examples of what instruction means, although it does not clarify that instruction is optional in the schema.

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?

The description states a specific verb and resource: "Rewrite a post draft with an instruction." The ctnt_ handle reference links it to content drafts and helps distinguish it from reply/comment draft tools, though it does not explicitly contrast it with the generic rewrite_draft sibling.

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?

It gives clear usage context: this rewrites rather than publishes, and the rewrite runs in the background so the agent should call list_content_drafts afterward to read the result. It does not explicitly say when to choose rewrite_draft versus rewrite_content_draft, so it stops short of full alternative guidance.

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