Flatten a PDF

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds real behavioral context by explaining that form fields become baked into the page and permanently lose editability, which is the core consequence beyond what the annotations convey.

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?

A single, front-loaded sentence that states the action and its consequence with zero wasted words. Nothing repetitive or filler.

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?

The tool is simple (2 fully-described params) and has an output schema, so return values need no explanation. The description covers the mutation's effect, and annotations carry idempotency; only edge behavior (e.g. a PDF with no form fields) is unaddressed, a minor gap.

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 100%, so both 'input' and 'output' are fully documented in the schema, including the no-overwrite rule. The description adds no parameter-level detail, which is acceptable at this coverage level, giving the baseline of 3.

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 gives a specific verb ('Make form fields part of the page') and a precise resource (PDF form fields), with the resulting effect clearly stated. An agent can distinguish this from pdf_fill_form, though the description never names a sibling explicitly to route the choice.

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?

Usage is only implied: the phrase 'so their values show everywhere and can no longer be edited' suggests this is used after filling a form to freeze values. There is no explicit when-to-use statement, no prerequisite (e.g. a filled form must exist), and no named alternative such as pdf_fill_form.

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