Review an exact render batch

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), yet the description adds real value: it discloses that this performs no key load, no dry run, no provider pricing and no rendering, and states the tool's evidentiary limits. Disclosing what the review cannot prove is exactly the kind of context annotations cannot carry.

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 tight sentences with the scoping constraint ('Local only') front-loaded and no filler. It is telegraphic and jargon-heavy, but every clause carries distinct information.

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-only, fully-schema-documented tool with no output schema, the description supplies the key context an agent needs: local-only behavior, the hash binding, and the limits of what the review proves. Return values are the one omission, acceptable given no output schema.

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 schema documents account and renders thoroughly (ordering, 1-10 items, template_id vs elements). The description only reframes these as 'ordered payloads' and 'selected profile', adding little beyond the structured fields, so the baseline 3 applies.

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+resource: validate ordered payloads and bind them plus the selected profile to SHA-256, then display the proposed calls and hash. The scope ('Local only', no rendering) makes it distinguishable from submit_render_batch, though it never names a sibling explicitly.

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?

Usage is implied by the negatives ('no key load, dry run, provider price or actual rendering'), which tells an agent this is a pre-submission review, but no alternative tool is named and there is no explicit 'use this before X' instruction. The validate_render.dry_run crossover is only hinted at in the schema, not routed in the description.

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