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

The description adds significant behavioral context beyond the annotations: it states the source renders are left untouched (aligning with destructiveHint=false), mentions billing as one additional render, explains authentication requirements (API key with `render` scope), and describes the failure behavior for invalid IDs. No contradictions with annotations.

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 a single, dense paragraph that front-loads the core action. Every sentence adds value—covers scope, constraints, prerequisites, behavior, return format, and billing. No wasted words.

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?

Given the tool's moderate complexity (2 parameters, one required array, no output schema), the description fully covers purpose, constraints, ordering, error handling, return format, authentication, and billing. It is complete for an agent to select and invoke the tool correctly.

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%, so baseline is 3. The description reinforces the schema's details (order of IDs, failure condition, labeling) but does not add new semantic dimensions beyond what the parameter descriptions already provide. The description is consistent but not additive.

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 verb 'concatenate' (merge), the resource 'existing renders', and the output 'single new PDF'. It distinguishes itself from sibling tools by explicitly noting it is 'the composition step after several render_pdf / convert_document / edit_pdf calls' and cannot merge arbitrary URLs or raw bytes.

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 description provides explicit guidance on when to use this tool (after rendering or conversion steps), what it cannot do (merge arbitrary URLs or raw bytes), prerequisites (IDs must belong to the account and point to completed renders), failure conditions, and API key requirements. It clearly differentiates from siblings like split_pdf or render_pdf.

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