Delete PDF pages

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

Annotations already declare the write/mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely new context: the file is read and written locally and never transmitted. It does not address overwrite/force behavior or what happens with out-of-range pages, but it materially enriches the safety picture beyond the annotations.

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, no filler, with the core operation front-loaded and the local-processing reassurance placed second. Every clause 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?

No output schema exists, so the description needn't explain return values, and all four parameters are covered by the schema. The local-only guarantee rounds out the picture; only edge cases (invalid page numbers, overwrite resistance) are left undocumented, which is minor for a straightforward file transform.

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% — every parameter including the 1-based page-range syntax ('2,5-7') and the force overwrite flag is already documented in the schema. The description adds no parameter-level detail, so 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 and resource ('Remove the listed pages') and adds the ordering guarantee, which lets an agent distinguish it from pdf_split or pdf_organize. It stops short of explicitly naming a sibling alternative, but the operation is unambiguous.

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 implied by the wording but there is no explicit when-to-use guidance or named alternative (e.g., pdf_split for extracting pages, pdf_organize for reordering). An agent must infer that this is the page-removal tool from name and description alone.

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