pdf_rotate

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

No annotations are provided, so the description carries full burden. It mentions the rotation action but fails to disclose critical behavioral traits: whether it modifies the original file (likely not, given output parameter), requires specific permissions, handles errors (e.g., invalid file paths), or has side effects like creating new files. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste. It front-loads the core action ('rotate pages of a PDF') and specifies the angles without unnecessary elaboration, making it easy to parse and understand quickly.

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?

Given the tool's complexity (mutation with 4 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success status, error messages) or behavioral nuances like file overwriting. For a PDF manipulation tool among many siblings, more context is needed to guide proper use.

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 the schema fully documents all parameters (file, output, angle, pages). The description adds no additional meaning beyond what's in the schema, such as explaining angle units or page numbering conventions. Baseline 3 is appropriate when the schema does all the work.

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 the verb 'rotate' and the resource 'pages of a PDF', specifying the exact rotation angles (90, 180, or 270 degrees). It distinguishes from siblings like pdf_reorder (rearranges pages) or pdf_extract_pages (removes pages), making the purpose specific and unambiguous.

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 description provides no guidance on when to use this tool versus alternatives like pdf_reorder for page arrangement or pdf_extract_pages for removal. It lacks context about prerequisites (e.g., file must exist) or exclusions, leaving the agent to infer usage from the name alone.

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