pdf_rotate_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing beyond the raw action. It does not mention rotation direction or units, page indexing, whether the operation is destructive, or what the output looks like.

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 concise and to the point, but it is overly sparse. It is a single short sentence that states the core function yet lacks necessary detail about parameters and behavior, making it under-specified rather than efficiently complete.

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 definition is incomplete for a mutation operation: no annotations, no parameter explanations, and a one-line description. Although an output schema exists, it does not clarify the operation's semantics, leaving important behavior ambiguous.

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?

The schema descriptions coverage is 0%, and the description does not compensate by explaining any of the three parameters. It omits details such as allowed rotation values (e.g., 90, 180, 270) and whether page_number is zero- or one-based.

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 action ('Rotate') and the target ('a page in a PDF'), which makes the tool's purpose immediately identifiable. It distinguishes from sibling tools like pdf_delete_page or pdf_crop_page because it specifies a distinct operation, though it does not elaborate on rotation specifics.

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 guidance on when to use this tool versus other PDF manipulation tools. The description does not state prerequisites, whether the operation modifies the file in-place or produces a new file, or any context for typical usage.

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