Read an exact render batch

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

Adds real context beyond annotations: prevalidation of all IDs, stop-on-failure semantics with completed-status records, and the absence of paging/auto-poll/download/spent-credit recovery. Annotations already cover readOnly/idempotent, so this extra failure-mode and non-feature disclosure is genuine added value.

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?

Three dense, front-loaded sentences with no filler; the count/scope constraint leads and exclusions are packed efficiently at the end.

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 read tool with no output schema and full annotation coverage, the description supplies the important behavioral envelope (prevalidation, stop-on-failure, no paging/poll). It could note what a 'completed status record' returns, hence not a 5.

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 50%, and the schema itself documents the ID format constraints (pattern, length, no URL/slash) thoroughly. The description adds the 1-20 count and 'distinct' constraint, which the schema also encodes via minItems/maxItems/uniqueItems, so marginal added meaning.

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 precise verb+resource+scope: 'Read one to twenty distinct render IDs sequentially in one project.' The batch/sequential constraint plus the count bound clearly distinguishes it from get_render (single) and preview_render_batch.

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?

Implies usage via the sequential/prevalidation framing but never names the alternative tools (get_render, preview_render_batch, submit_render_batch) or states when to prefer this over them. Exclusions are behavioral rather than routing guidance.

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