Organize PDF pages

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds a genuinely new behavioral trait — the file is processed entirely locally and never transmitted — which is exactly the kind of context annotations cannot express. It stops short of disclosing what happens when output already exists (only the 'force' param hints at this) or whether input can equal output.

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 short sentences, front-loaded with the core operation, then the unifying insight about delete/reorder/duplicate, then the local-execution note. Every sentence carries distinct information and nothing is padded.

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?

With no output schema, the description carries the return-value burden, and for a file-writing tool it adequately conveys that the result is a rebuilt PDF written to a path. Combined with 100% schema coverage and existing annotations, an agent has enough to call it correctly; the only minor gap is overwrite/force behavior, which is left to the schema.

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%, so all four parameters (input, pages, output, force) are already documented with format and 1-based indexing. The description restates the pages semantics (order matters, repeat to duplicate) but adds no syntax or constraint beyond the schema, so the 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 concrete verb+resource ('Rebuild a PDF') and immediately defines scope: which pages survive and in what order. It also makes explicit that reordering, deleting and duplicating are all this one operation, which implicitly separates it from siblings like pdf_delete_pages and pdf_rotate without the agent needing to open either schema.

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?

Gives clear operative guidance on what the tool does in each case (omit = drop, move = reorder, list twice = duplicate), which tells an agent when this tool subsumes other operations. However, it never names an alternative sibling (e.g. pdf_delete_pages, pdf_split) or states when NOT to use this, so routing is inferred rather than explicit.

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