delete_dashboard

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

With no annotations, the description carries full burden but only states the action. It doesn't disclose critical behavioral traits: whether deletion is permanent, requires specific permissions, affects linked resources, or returns confirmation. The existence of 'restore_dashboard_version' suggests potential reversibility, but this isn't mentioned.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable.

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 destructive tool with no annotations and no output schema, the description is insufficient. It lacks details on permissions, consequences, reversibility, error handling, or response format. Siblings like 'restore_dashboard_version' hint at versioning, but this context isn't integrated.

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 description adds meaning by specifying that the 'uid' parameter identifies the dashboard to delete. With 0% schema description coverage and only one parameter, this adequately compensates, though it doesn't explain UID format or sourcing (e.g., from 'get_dashboard_by_uid').

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') and resource ('a dashboard by UID'), making the purpose unambiguous. It distinguishes from siblings like 'get_dashboard_by_uid' (read) and 'update_dashboard' (modify), but doesn't explicitly differentiate from other destructive operations like 'delete_alert_rule'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing dashboard UID from 'get_dashboard_by_uid' or 'search_dashboards'), nor does it clarify if deletion is permanent or reversible (though 'restore_dashboard_version' exists as a sibling).

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