Review a render batch

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

Annotations already declare readOnly/idempotent/non-destructive safety, so the bar is lower, and the description adds genuinely new context beyond them: validation is 'local' (no provider round-trip) and it explicitly performs 'No provider state or price validation.' That scoping tells the agent what the tool will and will not catch, which is real behavioral 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 short sentences with no filler and the key scope constraint front-loaded. However, the compression is so aggressive that the text reads as internal jargon rather than an explanation, undermining the conciseness benefit.

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 tool with a very large nested schema, 0% parameter description coverage, and no output schema, the description is too thin. It never explains what the preview returns (a 'digest' is named but not defined) or how the agent should act on a successful validation, leaving the agent unable to use the result confidently.

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 0% across 3 parameters, so the description must compensate. It loosely frames the payload as '1–100 native image payload' (matching the items min/max) and notes the digest binds 'exact order, method/path, profile label and body,' but it does not explain the account, payload, or payload_file parameters or their required/optional status.

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 states a validation/review action over image payloads ('schema-validated 1–100 native image payload review'), which is a specific verb+resource. However, it never clarifies the relationship to its obvious sibling apply_render_batch, and the telegraphic phrasing ('Digest binds exact order, method/path...') forces the agent to already know the domain to parse the purpose.

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 explicit when-to-use guidance and no named alternative. The name implies a preview/dry-run and the sibling apply_render_batch is the natural counterpart, but the description never states that this should be called before applying a batch, nor when to skip it.

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