delete_dashboard

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

Annotations already carry destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds a permission requirement, which is useful context, but it does not disclose additional consequences such as permanence or cascading effects on widgets; given the annotation coverage, the added value is moderate.

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 a single, terse sentence that states the core action and a permission caveat with no filler. It earns its place and is front-loaded with the primary behavior.

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 one-parameter destructive tool with full schema coverage and annotations covering idempotency and destructiveness, this description is sufficient for an agent to invoke it correctly. No output schema exists, and the operation is simple enough that additional return-value documentation is unnecessary.

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 fully documents dashboard_id with a clear description, so the schema carries the parameter semantics. The description adds no further parameter detail, but no additional parameter information is needed.

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 the specific action ('Delete') and resource ('a dashboard'), making the tool's function unambiguous. It does not explicitly contrast with sibling tools like get_dashboard or update_dashboard, but the verb itself sufficiently distinguishes it from those alternatives.

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 one relevant prerequisite ('requires write permission'), which helps an agent determine whether the call is permissible. However, it does not explicitly state when to prefer this tool over alternatives or what to do when the prerequisite is not met; the usage context is mostly implied.

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