Check ESPHome capability

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond that: the tool is a gating check whose result depends on the relay/add-on topology, and it implies a capability answer rather than an action. It does not describe the shape of the 'not reachable' response, but for a read-only probe this is good.

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?

Front-loaded with the core answer (reachability and what is possible), then the environment note, then the usage trigger. It is somewhat dense with em-dash clauses, but every sentence carries weight and none is redundant.

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?

There is no output schema, so the description must convey what comes back; it does by naming the capability classes it reports (config listing/editing, streaming commands). Combined with the read-only annotation and full param coverage, an agent has enough to invoke and interpret it, though the exact response format remains unspecified.

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?

One optional parameter with 100% schema description coverage; the schema already explains instance_id and the cross-home refusal behavior in detail. The description adds nothing about the parameter, so the baseline 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+resource: reporting whether ESPHome is reachable and enumerating what is possible (config listing/editing and the streaming commands). It is clearly a capability probe, distinguishable from the actual action siblings (esphome_validate, esphome_compile, esphome_upload, esphome_logs, esphome_clean) that it names.

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 an explicit trigger: call this before telling a user that flashing or log-reading is unsupported. It also explains the environmental precondition (a VomeHome relay-connected Home Assistant running the Vome add-on) under which everything is available. It does not state when the tool is unnecessary, so it falls short of a 5.

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