Connect Home Assistant state bus

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

Annotations provide readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the description need not restate these. It does add that it creates a scaffold with network adapter nodes and safety notes, but it omits side effects such as whether it attempts to connect to the Home Assistant instance, modifies the existing project, or how reversible it is.

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?

A single 17-word sentence that front-loads the action and product. Every phrase earns its place, listing the key scaffold components without filler or repetition.

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 9 optional parameters and no output schema, the description should explain what the resulting scaffold looks like, how to use it, and how parameters shape the output. It names components but leaves the agent without enough context to validate the result or understand integration behavior.

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 only 22% (2 of 9 parameters described). The description hints at adapter_mode and entity/service mapping, but it does not clarify parameters like active, area_count, base_url, or parent_path. With such low schema coverage, the description should compensate more, but it only partially does.

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 uses a specific verb and resource: 'Create a Home Assistant state/service scaffold' and enumerates concrete components (REST/WebSocket adapter nodes, entity maps, service maps, physical-action safety notes). This clearly distinguishes it from generic WebSocket/MQTT bridge tools in the sibling list.

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?

No guidance is provided on when to use this tool versus alternatives like connect_mqtt_iot_bus or connect_websocket_control_bus. The description does not mention prerequisites (e.g., Home Assistant base URL or credentials) or exclusions, so the agent has to infer usage from the name/title alone.

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