delimit_agent_dashboard

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

Explicitly states it is a 'View' operation, implying read-only behavior. Lists the types of data shown (tasks, handoff history, ledger items, audit trail). No mention of side effects or access restrictions, but with 0 parameters and a view intent, this is adequate.

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 short sentences: first states the primary action, second enumerates content. No filler, front-loaded, every word 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 that an output schema exists (context signal), the description need not detail return values. It covers the essential purpose and data scope. However, could mention if filtering or interaction is possible, but overall complete for a dashboard viewer.

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?

No parameters in the input schema, so description naturally adds no parameter info. Schema coverage is 100%, meaning the schema fully documents absence of params. Baseline score of 4 is appropriate.

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?

Clearly states it is a 'View' operation for the 'multi-agent orchestration dashboard' with qualifiers (Pro). Immediately identifies the tool as a read-only dashboard, distinct from other agent tools that perform checks or dispatches.

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?

Does not provide any guidance on when to use this tool versus alternatives like delimit_agent_status or delimit_ledger_list. No explicit when-not-to-use or prerequisite conditions.

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