delimit_agent_dashboard

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

No annotations provided, so description carries full burden. It declares 'Side effects: read-only' and mentions the underlying call 'ai.agent_dispatch.get_agent_dashboard'. This is transparent, though could add details about caching or permissions.

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?

Well-structured and concise: title line, clear sections (when to use, when not, sibling contrast, side effects, args, returns). No wasted words, front-loaded with key info.

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?

Covers usage, side effects, and return structure. With an output schema present, the description provides adequate high-level guidance. Missing details about the 'Pro' requirement, but otherwise 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?

Schema coverage is 100% with 0 parameters. The description redundantly states 'Args: None', adding no value beyond the schema. Baseline is 3 per calibration rules.

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 'View the multi-agent orchestration dashboard (Pro)' with a specific verb and resource. It clearly distinguishes from siblings like delimit_agent_status and delimit_agent_dispatch in the usage guidelines.

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 states when to use ('one-shot read of all agent activity grouped by assignee/status'), when not to use ('for a single task's status use delimit_agent_status; to dispatch new work use delimit_agent_dispatch'), and contrasts with delimit_agent_status.

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