pdf_flatten

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

The description discloses that fields become non-editable and annotations are converted to static content. This provides clear behavioral insight beyond what annotations (none provided) would convey. However, it could mention if original file is modified or other side effects.

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?

Two sentences with no wasted words. The first sentence defines action and effect, the second adds usage context. Ideal length and structure.

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 straightforward tool with no output schema and a rich set of sibling tools, the description provides sufficient context. It explains what the tool does, its effect, and when to use it. Minor improvement: clarify that outputPath must differ from input to avoid overwrite.

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?

The input schema already describes both parameters with 100% coverage ('PDF file path' and 'Output path'). The description adds no additional parameter details, so the baseline score of 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?

The description clearly states the tool's purpose: flatten a PDF by converting form fields and annotations into static content. This distinguishes it from siblings like pdf_form_fill and pdf_merge.

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?

The description says 'Useful for finalizing documents before distribution,' which implies usage context but does not explicitly compare with alternative tools or state when not to use it.

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