Remove Label

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

Beyond the annotations (destructive=true, readOnly=false, idempotent=true), the description discloses the cascading effect ('removes the label from all entities, devices, and areas') and irreversibility, which the annotations alone do not convey. The Claude Desktop timeout note adds operational context, though it is client-specific rather than tool-semantic.

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 and warning are front-loaded effectively, but the long Claude Desktop workaround paragraph is verbose and tangential to the tool's own semantics, diluting the otherwise tight structure.

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?

With an output schema present and annotations covering the safety profile, the description only needs to add cascade behavior and irreversibility, which it does. Nothing essential for a correct call 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 coverage is 100% so the schema already documents label_id, giving a baseline of 3. The example call showing the ID argument in use adds a small amount of value beyond the schema, warranting a slight bump.

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 label') and reinforces it with 'Removes the label from the label registry'. This cleanly separates it from siblings like ha_config_set_label and ha_config_get_label.

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?

Points the agent to the right companion tool ('Use ha_config_get_label() to find label IDs') and provides a concrete invocation example. It gives clear context but does not state explicit when-not-to-use conditions or compare against other removal tools.

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