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

With no annotations, the description carries the full behavioral burden; it does deliver the key fact that output is base64 of the rotated PDF rather than an in-place mutation. It omits whether the original is altered, any file-size or page-count limits, and error behavior for invalid page specs, which matters for a stateless transform.

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 tight sentences that front-load the operation and then the return value; every clause earns its place with no filler or restatement of the tool name.

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 simple three-parameter transform with full schema coverage and no output schema, stating the base64 return is enough to call it correctly. Only minor gaps remain around limits and failure modes, so it falls just short of complete.

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% and the schema already documents all three parameters, including defaults and the '1-3,5' page format. The description only adds the loose phrase 'some or all pages', which duplicates what 'pages' already conveys, so baseline 3 applies.

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?

States a specific verb (rotate), resource (PDF pages), a bounded parameter domain (90/180/270), a scope option (some or all pages), and the return format in base64. No sibling (pdf_merge, pdf_split, pdf_text, pdf_info) overlaps with rotation, so the agent can select it unambiguously.

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?

Usage is implied by the verb and scope phrase, and there is no competing rotation sibling to route away from. However, there is no explicit when-to-use context, no prerequisites, and no pointer telling the agent to first inspect pages with pdf_info before choosing a page range.

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