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

Annotations already disclose readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false. Beyond that, the description usefully adds the read+write permission requirement and the 'follow the primary nextAction' envelope contract. However, the central behavioral instruction (confirm:false preview, then confirm:true) cannot be executed because no such parameter exists, which undermines the disclosure.

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?

Four tight sentences with the purpose, permissions, operation list and workflow front-loaded in that order. Minor waste in restating the operation enum verbatim, but nothing is padded.

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 an output schema present, the description is right not to explain return values, and it correctly calls out the permission requirement for a multi-operation generator. The gap is that the two-step confirmation flow is unexecutable as written, leaving the agent without a valid preview/confirm procedure for a non-idempotent write operation.

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 all five parameters are already documented and the baseline would be 3. The description's only parameter-level addition is the non-existent 'confirm' flag, which actively misleads rather than informing; the operation list simply repeats the enum. Introducing a phantom parameter is worse than adding nothing.

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 concrete verb and resource ('Generate a PDF of a saved document or report') and enumerates the four supported operations, so an agent knows exactly what it produces. It does not name or distinguish any sibling tool, though no sibling in the list also produces PDFs, so confusion risk is low.

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 workflow and prerequisite guidance ('Requires both read and write access', preview-then-confirm) but never says when to choose this over alternatives or what the preconditions are for each of the four operations. The preview/confirm advice references a 'confirm' parameter that does not exist in the input schema (additionalProperties: false), so an agent following it verbatim would fail validation.

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