delete_dashboard

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

No annotations are provided, so the description must fully disclose behavior. It states 'Delete' but does not clarify if deletion is permanent or reversible, what happens to contained cards, or any side effects. The existence of an output schema is mentioned but not detailed.

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 short and front-loaded with the core purpose. However, it includes structured Args/Returns that partially repeat the schema, which is acceptable but not maximally efficient. The information density is low given the tool's simplicity.

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 deletion tool, the description lacks essential context about permanence, required permissions, or the impact on associated items. The output schema exists but is not described, and the description does not compensate for the missing annotations. Overall, it feels incomplete for safe agentic use.

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?

Schema description coverage is 0%, yet the description for dashboard_id only restates the parameter name without adding meaning about data sources, validation rules, or how to obtain the ID. The single parameter is self-explanatory, but the description adds little value beyond the name.

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 'Delete a dashboard from Metabase', specifying the verb and resource precisely. It distinguishes from sibling tools like archive_card (which deletes cards) and update_dashboard (which modifies).

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 archiving or deactivating dashboards. Does not mention prerequisites like ownership or permissions needed for deletion.

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