delimit_agent_dashboard

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

With no annotations, the description fully covers transparency: states it's read-only, names the underlying function call (ai.agent_dispatch.get_agent_dashboard), and outlines the return structure. 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?

Well-structured with labeled sections (main purpose, when to use/not use, sibling contrast, side effects, args, returns). Every sentence adds value; no redundancy.

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 zero-parameter, read-only dashboard tool, the description covers purpose, usage, side effects, underlying function, and return structure. An output schema exists but description adds enough context for invocation.

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 has zero parameters, schema coverage 100%. The description explicitly states 'Args: None', making it clear. Baseline for no params is 4.

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 is for viewing a multi-agent orchestration dashboard, and distinguishes it from sibling tools (delimit_agent_status returns raw records vs. aggregated view). The verb 'View' and resource 'multi-agent orchestration dashboard' are specific.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance, including alternatives (delimit_agent_status for single task status, delimit_agent_dispatch for dispatching work). Sibling contrast further clarifies.

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