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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: the state machine (running, failed, or done) and what a completed batch contains. "Charges nothing" adds billing context absent from annotations. Minor redundancy in restating "Read-only," but the state semantics are real 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?

The operation and its return semantics are front-loaded in a compact two-sentence block with no filler. However, the long enumeration of return fields is largely redundant given an output schema exists, spending words that could have covered batchId instead.

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 annotations and an output schema present, the description need not explain return shapes, yet it omits the two things an agent still needs: where the batchId comes from and whether/how often to poll. For a status-check tool, missing polling guidance and missing linkage to the batch-creation sibling leaves a real gap.

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 0% and the sole parameter batchId has a strict 64-hex pattern that is completely unexplained. The description says "a Show 3 batch" without stating that batchId is the identifier returned by the batch-creation tool, nor how to obtain or format it, so it fails to compensate for the coverage gap.

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?

"Read a Show 3 batch" states a clear verb and resource, and the description goes on to define what the batch yields (three directions with directionId, title, summary, screenshot, preview link, and create_site arguments). It is recognizably a status/polling read, but it never names the sibling that creates the batch (iter0_show_three), so sibling differentiation is left implicit.

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 only implied: the mention of a batch and its running/failed/done states suggests polling after a batch is started, but the description never says when to call this versus iter0_show_three, iter0_get_design, or iter0_get_site_status. "Read-only; charges nothing" hints at a safe free poll but is not framed as guidance.

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