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

Annotations already declare readOnlyHint=false and destructiveHint=false, lowering the bar. The description adds that a result file is returned and that rotation can be limited to selected pages, but says nothing about whether the original is preserved or how pages/angle interact.

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?

Three short, front-loaded sentences with little waste. 'Accepts pdf' is slightly redundant with the schema but adds the format restriction plainly.

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 mutation tool with a nested options object and no output schema, the description is thin: it never explains page-selection syntax, rotation direction semantics, or output handling. An agent would need to guess at options behavior.

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 coverage is 100% at the top level, so the baseline is 3. The description adds no detail about the options object—angle values (90/180/270), the 'pages' string format, or how 'scope' interacts with 'pages'—which the schema itself leaves undocumented.

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?

Specific verb+resource: 'Rotate all or selected pages of a PDF' states the operation and its scope. It doesn't differentiate from nearby siblings like reorder-pdf or crop-pdf, so not a 5.

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 when-to-use/when-not guidance and no mention of alternatives such as reorder-pdf when page order also needs changing. The 'all or selected pages' phrasing implies scope but gives no selection criteria.

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