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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds real value by disclosing the cascade (widgets and Charts view are destroyed) and the required user confirmation step, plus reversibility via restore. It does not say whether deletion is immediate or soft/delayed, or what permissions are required, which keeps it from a 5.

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 short sentences: what is destroyed first, then the confirmation rule, then the undo path. Every sentence earns its place and nothing is repeated from the annotations.

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 single-parameter mutation with an output schema and rich annotations, the description covers cascade effects, user confirmation, and recovery. Only permission requirements and deletion timing (immediate vs delayed) are missing.

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?

With one parameter and 0% schema description coverage, the description must compensate. It tells the agent that the target dashboard must be identified before the call, but never says that `dashboardId` is a numeric ID or where to obtain it, leaving the parameter's format and provenance unclear. Partial compensation only.

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?

States a specific verb (Delete) and resource (dashboard), and adds scope: it removes the dashboard plus its widgets and its Charts view. It also names the sibling that reverses it (`dashboard.restore`), so an agent can distinguish this from restore/read/update without opening any schema.

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?

Explicitly says to confirm with the user and identify the target dashboard before calling, which is exactly the guidance an agent needs for a destructive action. It also points to `dashboard.restore` as the recovery path. It does not name a read/lookup tool (e.g., dashboard.read) for finding the ID, so it stops just short of full routing guidance.

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