Connect Home Assistant state bus

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

Annotations already declare the tool as non-read-only, non-destructive, and open-world. The description adds that it creates a scaffold with specific components and includes safety notes, but it does not disclose side effects, authentication requirements, or what happens if the scaffold already exists. Some value is added beyond annotations, but depth is limited.

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 description is a single sentence that is front-loaded with the core action and target, containing no filler or redundant details. It efficiently conveys the high-level purpose, though it sacrifices depth for brevity.

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 parameters, no output schema, and no return-value documentation, the description is too sparse. It lists scaffold components but does not explain what the tool returns, prerequisites like a reachable Home Assistant instance, or how the scaffold integrates with the existing project. The description leaves significant gaps for an agent trying to invoke the tool correctly.

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 only 22% (2 of 9 parameters have descriptions). The description hints at adapter_mode via 'REST/WebSocket adapter nodes' but does not explain the meaning of any parameters, their defaults, or how they relate to the scaffold. It fails to compensate for the low schema coverage.

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 clearly states the action ('Create') and the specific resource ('Home Assistant state/service scaffold'), and details the scaffold's components (REST/WebSocket adapter nodes, entity maps, service maps, safety notes). This distinguishes it from sibling connect_* tools that target other systems like MQTT or serial devices.

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?

The intended use is implied by the name and description (connecting to Home Assistant), but there is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description does not say 'Use this when...' or 'For other integrations, use...'.

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