delimit_agent_status

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

Discloses 'Side effects: read-only' and the underlying API call (ai.agent_dispatch.get_agent_status). Since no annotations are provided, the description fully covers behavioral traits.

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?

Short, front-loaded, uses bullet points effectively. Every sentence adds value.

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?

Given one parameter, no required fields, good schema, and an output schema exists, the description is complete. It explains purpose, usage, and side effects sufficiently.

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 already has a detailed description for task_id that matches the text in the description. The description adds no new meaning beyond what the schema provides; schema coverage is 100%.

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 'Check status of dispatched agent tasks (Pro)', specifying the resource and action. It also distinguishes from siblings like delimit_agent_dispatch and delimit_agent_complete.

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?

Explicitly provides 'When to use' and 'When NOT to use' with specific sibling tool names, plus a sibling contrast with delimit_agent_dashboard.

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