Edit pages (rotate / delete / reorder)

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

The description explains the order of operations (delete first, then rotate and reorder) and clarifies that rotate page numbers refer to source PDF while reorder uses post-delete positions. Without annotations, this provides good transparency, though it could mention that the output file overwrites without warning.

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, front-loaded with the main purpose and operation order. Every sentence adds value without redundancy.

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?

Given the complexity of combining delete, rotate, and reorder with different page references, the description covers the essential nuances. However, it could explicitly state that the output file will be overwritten if it exists.

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?

All parameters have schema descriptions (100% coverage), but the tool description adds crucial context about the order of operations and page numbering semantics for rotate and reorder, which are not present in the schema. This significantly aids correct usage.

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 title and description clearly state the tool edits PDF pages by deleting, rotating, and reordering. It distinguishes itself from sibling tools like extract_images, merge, and split, which perform different operations.

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 implies usage for combined page edits ('in any combination') but does not explicitly state when to use this tool versus alternatives. No when-not or alternative tool guidance is provided.

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