Cheap status of a Clanker run

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

Annotations already show readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds valuable behavioral context: non-blocking nature, stall detection field (suspected_stall), and that it returns current plan and tool_calls. No contradictions.

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, no unnecessary words. First sentence clearly lists return fields. Second sentence clarifies behavior. Every sentence 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?

For a simple tool with one parameter and no output schema, description is complete: explains return structure, non-blocking nature, stall detection. Could mention it is a lightweight check without side effects, but overall sufficient.

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?

Single parameter 'id' with schema description 'Run id'. Schema coverage is 100%, so description does not need to add much. The tool description does not elaborate on the parameter beyond what schema provides, which is acceptable but not additive.

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?

Description clearly states what the tool does: returns a specific set of fields including status, plan, tool_calls, last_event_age_ms, suspected_stall. Distinguishes from sibling like clanker_wait by explicitly saying 'Does not wait.'

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?

Implied usage: use for quick status check without waiting. But no explicit when-to-use/when-not-to-use or alternative references (e.g., 'Use clanker_wait to block until completion'). Only 'Does not wait' hints at distinction.

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