pdf_delete_pages

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

The description discloses important behavioral traits beyond annotations: it states that AcroForm fields on remaining pages are preserved, explains the flatten option's effect ('bake field values into static content'), and adds the constraint 'Cannot delete every page.' This provides valuable context that annotations (which are minimal) do not cover.

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?

The description is three sentences long, each earning its place: first sentence gives purpose, second adds behavioral note on forms, third introduces flatten and constraint. It is front-loaded with the core action and contains no superfluous text.

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 description covers the main action, key behaviors, and constraints. It does not explicitly state that the original file is left unmodified (implied by outputPath) or error conditions. For a tool with 4 parameters and no output schema, it is largely sufficient, though a brief note on side effects could improve completeness.

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 baseline is 3. The description adds meaning by explaining the flatten parameter's effect on form fields and the limitation that not all pages can be deleted. However, for filePath and outputPath, it adds nothing beyond the schema. The 'pages' parameter description in schema already includes examples.

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 'Delete specific pages from a PDF, keeping the rest in their original order,' which is a specific verb and resource. It distinguishes from siblings like pdf_split (which splits into separate files) and pdf_reorder_pages (which changes order). The added note 'Cannot delete every page' further differentiates it.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where pdf_split or pdf_reorder_pages might be more appropriate. There are no explicit when-to-use or when-not-to-use instructions, leaving the agent to infer usage context.

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