delete_dashboard

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

The description discloses that deletion is permanent ('permanently removes'), which is key for a destructive operation. However, it lacks details on authorization requirements, whether cascading effects occur, or what the response looks like.

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?

Three sentences with a clear heading and structured Args block. Every sentence is necessary; no superfluous content.

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?

The description covers the basic operation but omits return value, error scenarios, and preconditions. Given the tool's simplicity and lack of annotations, more context (e.g., idempotency, permissions) would improve completeness.

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 Args block lists parameter names and provides brief labels ('Project ID', 'Dashboard ID'), which adds some context beyond the bare schema. With 0% schema description coverage, the description partially compensates but does not explain types, formats, or constraints.

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 custom dashboard' and emphasizes permanent removal, providing a specific verb and resource that distinguishes it from sibling tools like update_dashboard or create_dashboard.

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 over alternatives, or prerequisites such as requiring the dashboard to exist. Does not indicate scenarios where deletion is appropriate or contraindicated.

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