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

Annotations cover the safety profile (destructiveHint=false, idempotentHint=false), and the description adds value beyond them: it discloses that a new artifact_id is returned, that the download_url expires after about an hour, and critically that degrees are 'added clockwise to each page's current rotation' — explaining the non-idempotent accumulation. It does not state whether the source artifact is left intact.

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?

Four short sentences, front-loaded with the operation and its constraints. There is mild redundancy — the degree values 90/180/270 are stated twice — but no filler or padding that would obscure the actionable content.

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 mutating tool with rich annotations and an output schema, the description covers what changes, the direction of rotation, the accumulator behavior, and the return shape and link lifetime. The remaining gap is the unspecified 'pages' selector syntax and whether the input artifact is preserved or replaced.

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% and the nested rotations objects are left as untyped additionalProperties, so the description is doing the heavy lifting: it defines rotations as a list of {pages, degrees}, enumerates the legal degree values, and clarifies the additive-clockwise semantics. It falls short on the format of the 'pages' selector (single page, range, or comma list).

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?

Names a specific verb and resource (rotate pages) plus the operation's scope: named pages only, by 90/180/270 degrees. An agent can immediately distinguish it from adjacent siblings like reorder_pages, delete_pages, and extract_pages, which perform different transformations on the same resource.

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 explicit when-to-use guidance, no when-not-to-use, and no named alternative. The only contextual hint is the leading 'Free.' cost note; the agent must infer that this is the tool for rotation rather than reordering or deletion from the verb alone.

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