Soft-delete (archive) a dashboard

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

The description discloses key behaviors: soft-delete, history retention, and template deletion restriction. With no annotations, the description carries the full burden, and it mostly succeeds but could mention reversibility or permissions.

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 two sentences, front-loading the main action and adding important constraints. Every sentence adds value with no redundancy.

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 tool's effect (soft-delete, history retention) and a constraint (templates). It lacks detail on return value or error behavior, but for a simple single-param tool it is mostly complete.

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' is fully described in the schema as 'Dashboard UUID.' The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Title and description clearly state the tool performs a soft-delete (archive) on a dashboard, specifying that history is retained and templates cannot be deleted. This distinguishes it from siblings like dashboard_update or dashboard_create.

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 description implies when to use the tool (to remove from list but keep history) and includes a constraint (templates cannot be deleted). However, it lacks explicit guidance on when not to use it or comparisons to alternative archive/delete tools among siblings.

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