pdf_rotate

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

No annotations are provided, so the description carries the full burden of explaining behavior. It reveals that rotation is the operation, but does not mention what happens to the output file, whether it overwrites input, how idempotency_key behaves, or what errors or limitations exist.

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 short and front-loaded, stating the core operation first and keeping the price note to a single word. However, it is too sparse to compensate for the missing parameter and behavioral details.

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 five parameters, no output schema, and no annotations, the description is incomplete. An agent cannot reliably determine how to specify pages, where the output goes, or what the response will look like, making this inadequate for confident invocation.

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 0%, and the description does not explain parameters such as pages, output_path, or idempotency_key. The angle parameter is partially covered by the description, but the meaning of page-range syntax and output behavior is left entirely to inference.

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 identifies the operation: rotating PDF pages, with the supported angles enumerated. It distinguishes itself from sibling tools like pdf_merge, pdf_split, and pdf_compress by naming the specific transformation.

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?

No guidance is given about when to choose this tool over alternatives, nor about prerequisites, page-range syntax, or cost beyond the terse '1 cent.' The usage context is implied by the tool name and angle options rather than explicitly stated.

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