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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does not indicate whether the operation is read-only, whether it supports filtering by status or correction_id, whether pagination applies, or what the response shape is. The minimal description leaves significant behavioral ambiguity.

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?

The description is one sentence, concise, and front-loaded with the action. Every word contributes to the purpose; the status list is directly relevant. No redundant or extraneous content.

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?

Despite having an output schema, the tool has no annotations and a very sparse description. It lacks crucial context such as how to filter by status or correction_id, whether the statuses are mutually exclusive, or how the 'limit' parameter behaves. For a read-type tool with optional parameters, this is insufficiently complete.

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?

The schema has 0% description coverage, so the description must compensate. It does list the allowed statuses, which overlap with the enum in the schema, but it does not explain the 'limit' or 'correction_id' parameters or how they affect the result. Thus it adds marginal value beyond the schema, but not enough.

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 clearly states the tool checks the status of submitted corrections and enumerates the possible statuses. It uses a specific verb ('Check') and a specific resource ('status of submitted corrections'), making it distinct from sibling tools like get_correction_chain or submit_correction.

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 guidance on when to use this tool versus alternatives. It does not mention that it should be used after submitting a correction, nor does it exclude cases like checking a specific correction by ID. The description is purely a statement of function, with no usage context or exclusions.

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