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

With no annotations, the description carries the full behavioral burden. It hints that a private secret grants access to a submission's state, but says nothing about read-only safety, error behavior on an invalid or mismatched secret, rate limits, or what the returned state contains.

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 front-loaded sentence with no filler. It is efficient, though its terseness leaves the reader with unanswered questions rather than fully earning its brevity.

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 two-required-parameter tool with no annotations, no output schema, and half the parameters undocumented, the description is too thin. It omits what 'state' means, whether the secret authenticates the caller, and how failures surface.

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%: agent_secret is well documented (base64url, 32 bytes) while submission_id has no schema description. The description loosely maps the two params to concepts ('your submission' and 'its private secret'), but adds no format or constraint detail beyond the schema, so it neither compensates for the gap nor adds much.

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 clear verb ('read') and resource ('your submission state'), which is more specific than the bare tool name check_status. However, it does nothing to distinguish this from siblings like verify_receipt or read_own, which also plausibly read submission-related data, so an agent gets no routing help.

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 explicit when-to-use, when-not-to-use, or named alternative. The phrase 'your submission' weakly implies you must own the submission, but nothing tells the agent how this differs from verify_receipt or read_own.

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