check_status

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 fails to disclose whether this is safe to poll repeatedly, if it's read-only, or what states the status might return. These are critical gaps for a status-checking tool.

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?

Two sentences with zero waste. The purpose is front-loaded ('Check the status...'), followed immediately by the parameter semantics. Every word earns its place.

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?

Adequate for a single-parameter tool with an output schema (so return values needn't be described), but clear gaps remain regarding behavioral traits (idempotency, polling safety) that are important for status-checking operations.

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?

With 0% schema description coverage, the description successfully compensates by explaining that 'request_id' comes from 'submit_request'. This provides crucial semantic context linking the parameter to the sibling tool's output, though it lacks format constraints or examples.

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 states a specific action ('Check') and resource ('status of a Soma request'). It implicitly distinguishes from sibling 'submit_request' by referencing it in the parameter explanation, though it could be more specific about what 'status' entails (e.g., completion state vs health check).

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?

The parameter description implies a workflow ('the ID returned by submit_request'), suggesting when to use this tool. However, it lacks explicit guidance on polling behavior, rate limits, or when NOT to use this versus alternatives.

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