Delete area

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds genuinely new context: the effect is immediate ('area disappears from the registry immediately') and irreversible ('there is no restore tool'). It stops short of noting permission/auth requirements or downstream effects on entities assigned to the area.

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?

Front-loaded with the action, then cleanly labeled Use when / Returns / Limits sections. Minor redundancy: the raw WS result is stated twice ('returns Home Assistant's result unchanged' and 'Returns: the raw WS deletion result').

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?

An output schema exists, so return-value explanation is optional, yet the description still covers the return, the mutation's immediacy, and the irreversibility — everything an agent needs before invoking a destructive one-parameter delete.

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 the single parameter already documents itself, including the pointer to areas_list_areas. The description adds no format or syntax detail beyond what the schema provides, so the 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?

States a specific verb and resource ('Delete a Home Assistant area by its area_id') and names the underlying WS command, making it trivially distinguishable from areas_create_area, areas_list_areas, and the other area siblings.

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?

Includes an explicit 'Use when: removing an area that is no longer used' line, giving clear positive context. It does not name an alternative or a when-not condition (e.g., what to do if the area still has devices), so it falls short of a 5.

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