delete_dashboard

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

With no annotations, the description carries the full burden. It discloses the meaningful protection constraint on the Overview dashboard, but says nothing about irreversibility, required permissions, or what happens to contained views/cards. A destructive tool with zero annotation coverage warrants more disclosure.

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, front-loaded sentences with no filler; the core action comes first and the constraint second. Every sentence earns its place.

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 single-parameter delete with no output schema and no annotations, the description covers the action and one guardrail. It is adequate but leaves irreversibility, permissions, and the identifier's semantics unaddressed.

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 single required parameter url_path has 0% schema description coverage, and the description never explains what it identifies or its format. With only one parameter, the description should have compensated for the documentation gap but does not.

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?

States a specific verb+resource ('Delete a custom dashboard') and scopes it with 'custom', which implicitly separates it from the sibling delete_dashboard_view and delete_dashboard_card operations. An agent can identify the target resource without opening the schema.

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?

Provides a clear when-not condition: the default Overview dashboard cannot be deleted. It stops short of naming alternatives (e.g., delete_dashboard_view for removing views) or stating prerequisites, so it is clear but not fully routing.

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