pdf_reorder

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

With no annotations, the description carries the full burden. It mentions the ability to duplicate pages by repeating numbers, which adds useful behavioral context. However, it does not disclose side effects (e.g., that the original file is not modified, a new output is created) or any requirements like file permissions.

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 concise sentences with no extraneous information. The purpose is front-loaded and every word 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?

The description covers the primary action and a key feature (duplication) but lacks details about the output format, whether pages are 0-indexed (though schema says 1-indexed), and does not mention error conditions or edge cases. Given the simplicity of the tool, it is minimally adequate.

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 three parameters are described in the schema with 100% coverage, so the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides, such as format details or constraints.

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 reorders pages and also notes it can duplicate pages by repeating numbers. This is a specific verb-resource pair that distinguishes it from sibling tools like pdf_extract_pages or pdf_delete_pages, though it does not explicitly contrast with them.

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 over alternatives, such as when to reorder vs. extract or delete pages. No context is given about prerequisites, file size limits, or typical use cases.

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