Flatten PDF form

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

The description says answers 'can no longer be edited, cleared, or extracted as form data,' which is a destructive change to form data. The annotations declare destructiveHint=false, creating a direct contradiction rather than useful additional context.

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 concise, front-loaded sentences with zero waste: it states the operation, then the consequence, then local execution. Each sentence earns its place.

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 3-param tool with full schema coverage and no output schema, the description covers operation effect, irreversibility, and local execution. It omits force/output handling details, but those are schema-documented, so it is close to complete.

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%, with all three parameters including force documented in the schema. The description adds no parameter syntax or meaning beyond what the schema already provides, so the baseline 3 applies.

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 ('Paint filled form values onto the page as static content') and resource (PDF form), plus the end state, clearly distinguishing this flattening operation from sibling PDF utilities.

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?

Implies use when you want to freeze filled form values, but gives no explicit when-not guidance or alternatives (e.g., versus pdf_protect or pdf_clean_metadata). Adequate but leaves routing to inference.

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