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

No annotations are provided, so the description carries the full burden. It implies a read-only lookup but never states permissions, whether it works for unpublished/sandbox items, or what happens when an item is still in draft; the only added detail is the status vocabulary.

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?

A single compact sentence that front-loads the verb and parenthesizes the status enum. Nothing is wasted, though it is arguably too sparse for a two-identifier lookup.

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, no annotations, and 0% parameter documentation, so the description is the only source of truth and it omits identifier semantics and return shape. For a status-check tool the status list helps, but the caller still cannot tell how to address a submission.

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 description says nothing about ref_id or submission_id. The key question — which identifier is required, and whether one can be used without the other (required count is 0) — is entirely unaddressed.

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 (check) and resource (status of your submissions) and enumerates the possible status values, which makes the tool's scope concrete. It does not explicitly distinguish itself from sibling submit_for_review or list_published, 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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer alternatives such as list_published or list_sandbox. The agent must infer that this is a read-only lookup on an already-submitted item.

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