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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add genuinely useful behavior the annotations cannot: the completion predicate and the fact that `total` lags while the queue drains. It still says nothing about error states, unknown batch_id, or result ordering.

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, front-loaded with what is returned and then the completion/lag caveats. Dense and waste-free, though the field-name shorthand (settled, expected_total) assumes the reader already knows the response shape.

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?

No output schema exists, and the description does much of that work by naming the return fields and the counters that signal completion. Adequate for a single-parameter read tool; it only lacks failure/not-found behavior and polling guidance.

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% and the single parameter batch_id has no explanation in either the schema or the description. The description spends its detail on output fields (settled, expected_total, total) rather than the input, so it does not 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?

States a specific resource and action: status of a photoshoot batch, plus the payload (per-item status and output_url). It is clearly a read-status tool, though it never names wait_for_job, the most likely alternative for the same resource.

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 by the completion rule ('done when settled >= expected_total'), which tells the agent how to interpret a poll but not when to call this versus wait_for_job or how often to poll. No explicit when-to-use or when-not-to-use guidance.

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