Tool Rotate Pages

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

With no annotations, the description must carry the full behavioral disclosure burden. It reveals the angle range and the default 'pages' behavior, but it does not disclose whether the original file is modified in place, what happens when 'output' is omitted, or what 'overwrite' actually controls. For a mutating PDF tool, these are critical safety-relevant behaviors.

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 very concise and front-loaded, with no wasted words. However, it is somewhat terse for a mutating tool with multiple undocumented parameters; a sentence or two about output/overwrite behavior would make it appropriately sized without adding clutter.

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 5 parameters, no annotations, and 0% schema description coverage, yet the description only covers the rotation action and the 'pages' default. It omits essential input-side behavior such as how 'output' and 'overwrite' interact and whether the original file is modified. The existence of an output schema does not compensate for these input-behavior gaps.

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%, so the description must compensate for the bare input schema. It adds meaning for 'angle' (allowed values) and 'pages' (default all), but leaves 'path', 'output', and 'overwrite' semantically unexplained. This is insufficient for a 5-parameter tool with no field descriptions.

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') with a specific resource ('pages'), and states exact supported angles (90/180/270 degrees). It also communicates that omitting 'pages' rotates all pages. This clearly differentiates it from the sibling tools, none of which are rotation tools.

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 intended use case is clear from the operation itself: rotate PDF pages by the specified angle. No sibling tool performs rotation, so there is no ambiguity about which alternative to choose. However, the description does not explicitly state exclusions or conditions such as output-file requirements or overwrite behavior.

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