Delete Dashboard Resource

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds genuine beyond-schema context: the downstream impact (custom cards fail to load) and an operational caveat about Claude Desktop timeouts/hangs. That extra failure-mode detail is valuable, though the timeout workaround is more incidental than core behavior.

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 core purpose, warning, example, and prerequisite note are front-loaded and efficient. The closing Claude Desktop timeout paragraph is three sentences of situational troubleshooting that dilutes focus, costing some conciseness.

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 single-parameter destructive mutation with an output schema, the description covers purpose, prerequisite discovery, downstream risk, and an example. Nothing an agent needs to call it correctly is 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?

Schema description coverage is 100% and there is only one required parameter with a clear schema description ('Resource ID to delete.'). The description only restates resource_id in the example, adding no format or lookup semantics beyond the schema, so baseline 3 applies.

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 opens with a specific verb+resource ('Delete a dashboard resource') and clarifies scope as removing a Home Assistant resource so it is no longer loaded on dashboards. It is clearly distinguishable from the sibling set_dashboard_resource / list_dashboard_resources tools.

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 instructs the agent to call ha_config_list_dashboard_resources() first to find the resource_id, and warns to ensure no dashboards depend on the resource before deleting. When-to-use and prerequisites are both covered, including a concrete example call.

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