rotate_pdf

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It reveals the API dependency and the uniform application to all pages, but does not state whether the original file is modified, what the default output behavior is, or any permission/network implications.

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 sentences totaling ~30 words, front-loaded with the primary action and directly followed by required input details. No wasted words.

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 tool has no annotations or output schema, and the description leaves ambiguity about output file behavior and return values. It also does not acknowledge the closely related rotate_pdf_page tool. While the essential invocation parameters are covered, the description falls short of fully contextualizing the operation.

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 schema documents file_path and rotation_type, but output_dir and output_file_name are only shown as nullable strings. The description confirms all four parameters and lists rotation_type's enum values, but adds no new semantic detail for the output parameters. With only 50% schema coverage, the description partially compensates but leaves behavior of output parameters unspecified.

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 ('Rotate') and resource ('all pages of a PDF') and explicitly states that rotation is applied uniformly, distinguishing it from sibling tools like rotate_pdf_page that target specific pages.

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?

It clearly describes the tool's purpose (rotate all pages uniformly) and mentions optional output parameters, but does not explicitly name alternatives or state when not to use it. The phrase 'all pages' implicitly contrasts with page-specific rotation, but the description stops short of explicit guidance.

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