Run a pipeline

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

Annotations already declare a non-read-only, idempotent, non-destructive write, and "write one new PDF" is consistent with that. The description adds the ordered-composition and 1–10 limit, but omits material behavior: whether the run is atomic when a middle step fails, whether the input file is left untouched, and any permission requirements.

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 sentences, zero filler: the composition/limit/side-effect claim is front-loaded, followed by the action list and a single inline example. Nothing is repeated from the schema or annotations.

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?

With an output schema present, return values need no explanation, and input/output path rules are carried by the schema. What remains thin for a 9-action composite is failure semantics — what happens to earlier steps or the output file if a later step fails — which an agent composing long pipelines would want before committing.

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 baseline would be 3. The description earns extra credit by surfacing the full action vocabulary and a concrete steps example ({"action":"rotate","options":{"pages":"1","angle":90}}), which orients the agent faster than parsing the oneOf const branches, though it adds no option semantics beyond the schema.

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 and resource ("Apply 1–10 steps in order and write one new PDF") and enumerates the valid step actions, which makes clear it is a composite of the per-operation siblings. It never names a sibling tool outright, so the routing distinction is inferable rather than stated.

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 1–10 ordered-steps framing implies this is for multi-operation workflows, but the description never says when to prefer this over calling pdf_rotate_pages / pdf_remove_pages / etc. directly, nor any exclusion (e.g. cannot be used with protected files). Usage is implied, not specified.

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