Remove Category

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

Goes well beyond the annotations by disclosing the cascading effect (removes the category assignment from all entities in that scope) and irreversibility, which the destructiveHint flag alone does not convey. It also flags a Claude Desktop hang workaround, adding operational context the structured fields cannot express.

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 purpose and warning are front-loaded and efficient, but the closing Claude Desktop timeout paragraph is disproportionate and reads like internal debugging notes rather than tool-selection guidance, diluting the core message.

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 covering return values and annotations covering the destructive/idempotent profile, the description fills the remaining gaps: cascade behavior, irreversibility, ID discovery, and a worked example. An agent has everything needed to call it safely.

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% and both parameters are documented in-schema, so the baseline is 3. The example clarifies the positional form and typical scope value ('automation'), but adds no constraints or edge cases beyond the schema.

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 category') and narrows the scope to the category registry, which cleanly separates it from siblings like ha_config_remove_label, ha_config_remove_scene, and ha_config_set_category.

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?

Gives a concrete invocation example and explicitly directs the agent to ha_config_get_category() to discover the required category_id. It lacks explicit 'do not use when...' or alternative-routing guidance, but the usage context is clear.

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