fix_page_size

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

No annotations are provided, so the description carries the full burden. It discloses the scope ('all pages') and units ('points') but does not mention whether the original file is modified in-place, if any permissions are needed, or what happens to the existing file. This leaves important behavioral context unstated for a mutation tool.

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 a single short sentence that conveys the essential operation without unnecessary words. It is front-loaded and clear.

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?

For a simple resizing tool, the description and complete schema together cover the key inputs. However, the lack of any behavioral disclosure about output handling or side effects (no annotations, no output schema) leaves some gaps, making this a minimum-viable description rather than a complete one.

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?

The input schema already provides complete descriptions for all four parameters (100% coverage). The description's mention of 'width and height' aligns with the schema and adds no new semantics beyond what is already documented, so the baseline of 3 is appropriate.

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 uses a specific verb ('Resize') and clearly identifies the resource ('all pages') and the key property (width and height in points). It distinguishes from sibling tools like crop_pdf or page_dimensions by specifying resizing.

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 does not provide explicit guidance on when to use this tool versus alternatives like crop_pdf or nup_pdf. However, the purpose is clear enough to infer usage for resizing page dimensions, so it meets an implied-usage threshold rather than being entirely absent.

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