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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The sentence "It does not modify the submission" largely restates those hints rather than adding new behavioral context such as latency, rate limits, or what happens when the submission is still pending. Useful but thin against an already-rich annotation set.

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?

Two sentences, both front-loaded: the usage trigger and payload contents come first, the non-mutation guarantee second. No filler, no repetition of the tool name or title.

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?

An output schema exists, so return-value documentation is not required, and annotations cover the read-only nature. The remaining gap is the required submissionId, left completely undefined despite 0% schema coverage, which is the one thing an agent must get right to call this tool.

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% for the single required parameter, so the description carries the full burden of explaining submissionId — and it does not name or describe it at all, saying only "a production brief previously submitted." It gives no hint about the expected identifier format (a string with minLength 8) or where an agent obtains it.

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 names a specific verb-plus-resource (retrieve the current human-review status of a production brief) and even enumerates what the status payload contains: review status, producer questions, available human estimate. That scopes it clearly against siblings like submit_production_brief or delete_production_brief, though it does not explicitly name an alternative tool.

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?

"Use this when the user wants..." is an explicit when-to-use trigger tied to a previously submitted brief, which correctly routes an agent away from submission or deletion flows. It stops short of naming when-not conditions or a specific fallback sibling such as estimate_production.

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