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

Annotations already declare destructiveHint=true and idempotent=false, so the description's job is to explain what is destroyed and why rendering is destructive. It adds the ownership constraint, the revision guard, and the explicit non-publishing scope, which is real value, but it never explains the destructive aspect (does it overwrite an existing PDF? create revision churn?). That leaves a notable gap against a destructive annotation.

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?

Three short sentences, front-loaded with the action and destination, then the prerequisite, then the exclusion. Nothing is wasted and the ordering matches how an agent needs the information.

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 2-parameter mutation with no output schema, the essentials are covered, but an agent still cannot tell what the call returns (a PDF id? a path?) or whether re-rendering overwrites prior output, which matters given destructiveHint=true and idempotentHint=false.

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 must compensate for both parameters. It does well for 'revision,' clarifying it is the opaque 64-char hash returned by get_document or save_document rather than a user-supplied number; 'id' is never explained beyond being implied by 'the current owned HTML draft'.

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 (render) and resource (the current owned HTML draft) plus the output destination (a PDF saved in Panta). The qualifier 'owned HTML draft' scopes it and 'Does not publish or send' fences off adjacent publish/send behavior, so an agent can separate it from save_document and get_document, though it never names a sibling explicitly.

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?

"Supply the revision returned by get_document or save_document" gives a concrete prerequisite chain and tells the agent which prior tools feed this one. The negative clause excludes publishing/sending. What's missing is a stated condition for when rendering is appropriate versus alternatives, or what happens on a stale revision.

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