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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description still adds real behavioral context: it states the operation is publicly accessible (no auth) and warns that the returned assessment does not establish provider operation success, which tells the agent how to interpret results.

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 dense sentence with no filler, and the core action is front-loaded. The trailing clauses are compact though slightly cryptic.

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 simple read-only tool with one param and annotations covering safety, the description is close to sufficient and adds an interpretation caveat. However, with no output schema it should say more about what is returned, and the mismatched 'status' framing leaves a 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 single required parameter submission_id is undocumented in both schema and description. The parameter is fairly self-explanatory by name, but the description does nothing 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?

The description gives a verb (read) and a resource (an accepted submission plus its documentary jobs), which is more than a tautology. But the tool name promises 'submission status' while the prose never mentions status, and it offers no differentiation from close siblings like get_job_status or validate_submission.

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 when-to-use guidance, no prerequisites beyond the scope word 'accepted', and no alternative named. 'Public access' is an authorization note, not usage direction, so the agent must guess when this tool applies versus get_job_status.

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