delete_dashboard

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

No annotations exist, so the description bears full responsibility. It does not disclose behavioral traits such as whether deletion is permanent, if it can be undone, or if permissions are required. The word 'Delete' implies a destructive action, but no further transparency is provided.

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 very concise, one sentence long, and front-loaded with the action. It wastes no words. However, it could include more useful details in the same space, such as the irreversible nature or required permissions, which would improve completeness without adding bulk.

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 the tool's simplicity (one parameter, no output schema), the description is minimally adequate. It lacks contextual information like the effect on related entities (e.g., dashboard cards, tabs) or confirmation needed. For a destructive tool, more completeness would be beneficial.

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 parameter 'id' has a description in the input schema ('Dashboard ID to delete'), and the tool description does not add extra information. With schema covering the parameter, a baseline of 3 is appropriate. No additional meaning is provided by the description.

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 verb 'Delete' and the resource 'a dashboard from Metabase'. It distinguishes from sibling tools like delete_card or delete_action by specifying dashboards. However, it doesn't elaborate on the type of deletion (soft/hard) or effects, so it's clear but not maximally specific.

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 on when to use this tool versus alternatives such as delete_dashboard_public_link or archive_dashboard (if exists). The description does not mention prerequisites, alternatives, or context. For a destructive action, more usage guidance is expected.

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