pdf_reorder_pages

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds crucial behavioral context not in annotations: 'Warning: form fields are not preserved' and 'Duplicates are allowed,' which are significant side effects for PDF manipulation.

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 sentences, zero waste. Front-loaded with purpose, followed by usage syntax, and ends with a critical warning. 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?

Complete for a reordering tool: covers input/output paths, page ordering syntax, and the important form field limitation. Could marginally improve by explicitly stating whether the source file is modified or if the operation is idempotent (though annotations cover the latter).

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?

With 100% schema description coverage, the schema already fully documents all three parameters including examples. The description echoes this information ('comma-separated string') but adds no additional semantic depth (e.g., explaining 1-indexing implications or path requirements) beyond the schema.

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 opens with a specific verb and resource ('Reorder pages in a PDF') that clearly distinguishes this from sibling tools like pdf_rotate_pages (orientation) and pdf_merge (combining files). The scope is immediately clear.

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?

Provides clear context on how to use the tool via the comma-separated example ('3,1,2') and notes that duplicates are allowed. However, it lacks explicit when-not-to-use guidance or named alternatives (e.g., distinguishing from pdf_rotate_pages).

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