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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds only the meaningful extra that the read is restricted to the authenticated agent's own submissions (an auth-scoping constraint). It says nothing about rate limits, pagination, or what a status value looks like.

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?

One tight sentence with the scope constraint front-loaded and no wasted words. It is efficient, though so terse that it omits information an agent needs, which borders on under-specification rather than pure conciseness.

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 no output schema, the description should describe what a 'submission status' response contains, and with a required 'id' of unclear meaning it should identify the key. Neither is present, so an agent cannot confidently form the call or interpret the result.

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 50%: apiKey is documented as a sensitive credential but the required 'id' parameter is undocumented in both schema and description. The description never clarifies whether 'id' is a submission id, mission id, or agent id, which is exactly the ambiguity the description should resolve.

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 ('Read') and resource ('submission status') and scopes it to the authenticated agent's own data, which distinguishes it from review_submission and get_request_status. It does not explicitly name the sibling it differs from, but the scoping phrase carries most of the differentiation work.

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 statement of when to call this versus get_request_status, get_mission, or review_submission, and no prerequisites or exclusions beyond the implicit 'own submission' scope. Usage must be inferred entirely from the name and the word 'own'.

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