Rotate Pdf

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

Annotations declare openWorldHint and idempotentHint, but the description adds no behavioral context beyond the operation itself. It does not state whether a new PDF is returned, how the source is consumed, what side effects occur, or whether the original file is modified.

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 sentence with no fluff and is front-loaded. It is concise, but it is so terse that it largely restates the tool's title, providing minimal added substance for an agent trying to understand the tool.

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 tool with 4 parameters and an output schema, the description is too thin. It does not explain how to select between source_url and file_base64, does not resolve the ambiguity that only angle is required, and provides no context about expected output or edge cases, making it incomplete for correct 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?

The input schema has 100% coverage with descriptive parameter details for angle, pages, source_url, and file_base64, so the description does not need to repeat them. However, it also adds no additional meaning, such as whether source_url and file_base64 are mutually exclusive or if one is required, so it stays at the baseline.

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 states a specific verb ('Rotate') and resource ('pages in a PDF'), which distinguishes it from sibling tools like merge_pdfs, split_pdf, or protect_pdf. However, it adds little beyond the title and omits the angle choices, relying on the schema to carry that detail.

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?

There is no guidance on when to use this tool versus alternatives, no mention of which input source (source_url vs file_base64) is needed, and no exclusions or prerequisites. Usage must be inferred entirely from the schema and tool name.

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