Remove a widget from a dashboard

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a 'hard-delete' (permanent) and confirms that the dashboard remains intact, but it does not mention any side effects (e.g., cascade deletions), authorization requirements, or rate limits. The disclosure is adequate for a simple delete but incomplete for a high-risk mutation.

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 a single sentence that immediately conveys the purpose and scope. It is front-loaded and contains no unnecessary words. Every part earns its place.

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 tool is simple, but the description lacks details about the return value (e.g., success confirmation or empty response) and error conditions (e.g., if the widget doesn't exist). It does not state prerequisites (e.g., the widget must exist). Given no output schema, the description could be more complete, but it covers the essential behavior.

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?

Both parameters (dashboard_id, widget_id) are fully described in the input schema with UUID format. The description does not add any additional meaning beyond the schema, such as why both are required or any constraints. With 100% schema coverage, the baseline is 3 and the description adds no extra value.

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 title and description clearly state that the tool removes a widget from a dashboard. The description specifies 'hard-delete' and clarifies that only the single widget is removed while the dashboard remains, distinguishing it from dashboard-level or bulk operations.

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 usage when a specific widget needs to be permanently removed from a dashboard, but it does not provide explicit guidance on when not to use it (e.g., for soft-delete or batch deletion) or mention alternative tools. While siblings include widget_create and widget_update, there is no other delete tool for widgets, so the context is clear but lacks explicit boundaries.

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