Hvac remove supply diffuser

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is fully covered by structured data. The description adds only the cryptic HVAC-001 rule reference pointing to bulc_knowledge_search; it does not disclose side effects such as whether removal cascades to connected ducts or whether the action is reversible.

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 sentence is short, front-loaded, and waste-free. The appended bracketed rule line is somewhat cryptic in phrasing but is brief and does not bloat the definition.

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 tool with annotations covering the safety profile and no output schema, the description is minimally adequate. It omits any note on network/duct dependencies or post-removal state, which would matter for an HVAC component, leaving it adequate but with visible gaps.

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 the single 'id' parameter carries its own description. The description's 'by ID' phrase merely restates the schema, adding no format, source, or lookup guidance beyond what is already present, so the baseline of 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 (Remove) plus resource (supply diffuser) and identifier (by ID), which cleanly separates it from siblings like hvac_add_supply_diffuser and hvac_update_supply_diffuser. It does not explicitly name or differentiate against near-neighbors such as hvac_remove_duct or hvac_remove_node, so it stops short of a 5.

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?

There is no when-to-use, when-not-to-use, or alternative-routing guidance. The bracketed '[bulc-mcp rules] HVAC-001 — bulc_knowledge_search' line hints at a compliance check but does not explain the condition under which this tool should be invoked or avoided.

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