delete_dashboard

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It adds a useful 'WARNING: This action is irreversible,' which is important for a destructive operation. However, it omits other potentially relevant traits such as permission requirements, effect on dependent resources, or error behavior, so it is only partially transparent.

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?

The description is two short sentences: the action and a critical warning. It is front-loaded with the primary purpose and contains no unnecessary filler, earning every character.

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 one-parameter delete tool, the description is minimally adequate: it states the action and the irreversible nature. However, it lacks context on usage conditions, alternative tools, or side effects, and the existence of an output schema does not relieve the need for behavioral guidance. There are clear gaps that a more complete description could fill.

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?

The input schema already provides a full description for the single parameter (dashboard_id: 'Dashboard ID to delete'), giving 100% schema coverage. The description adds no additional meaning or context beyond that, so a baseline score of 3 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?

The description clearly states the action ('Delete a dashboard') with a specific verb and resource, making the tool's purpose unambiguous. However, it does not distinguish itself from sibling delete tools like delete_monitor or delete_collector, so it stops short of full differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action and warns of irreversibility, which is a behavioral note rather than usage context.

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