Rotate PDF

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

Annotations already declare the write/openWorld/idempotency profile, so the bar is lower. The description adds genuinely useful context beyond them: the file is uploaded to an external service (conv2pdf) and the call is billed as one conversion, which informs quota-sensitive behavior.

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 tight sentences with the primary action front-loaded and no filler. Both sentences carry distinct information (what it does, and the upload/billing side effect).

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 single-operation tool with no output schema and full schema coverage, the description covers the action, direction, and side effects (external upload, quota cost). It omits only return/result details, which are largely implied by output_path in 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_path, output_path, rotation, password) are already documented, including the non-overwrite behavior. The description only restates the clockwise direction already present in the rotation enum description, adding no new parameter semantics.

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 specific verb and resource ('Rotates every page of a PDF') plus direction (clockwise) and scope (every page). This clearly distinguishes it from the conversion, merge, and extraction siblings, though it does not name any sibling explicitly.

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?

Usage is implied by the self-explanatory name and the note that the call 'counts as one conversion' (a quota consideration), but there is no explicit statement of when to use this versus alternatives such as convert_pdf_to_images or extract_pdf_pages for orientation fixes.

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