Delete Dashboard

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

Explicitly states it's a soft-delete and deactivates the public share link, adding valuable behavioral context beyond the annotations. No contradiction with annotations (destructiveHint=true, readOnlyHint=false).

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 efficient sentences, front-loaded, no unnecessary words. Every sentence adds value.

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 delete tool with a single required parameter and an output schema, the description is fully adequate. It covers the key effects (soft-delete, deactivation of share link).

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 coverage is 100%, so the schema already documents the parameter. The description adds no extra meaning beyond the schema's description of 'Dashboard business id to delete'.

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?

Clearly states the action (soft-delete) and resource (dashboard), with side effect of deactivating share link. Distinguishes from sibling tools like create_dashboard and update_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?

The purpose is clear for a delete tool, but no explicit when-to-use or when-not-to-use guidance is provided. The context is straightforward enough for an AI to infer.

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