Flash ESPHome firmware (OTA)

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

Annotations declare the mutation profile (destructive, openWorld, not read-only), and the description adds material context beyond them: write access is required, the build runs first so a failed build 'never reaches the device' (a safety-relevant guarantee for a destructive tool), and it runs over the VomeHome relay with no ports to open.

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?

Purpose is front-loaded and the following sentences each carry distinct operational information (auth, build-then-flash ordering, relay transport, unreachable-tool routing). Slightly long and drops into one marketing-flavored aside ('no cable, no manual step in the ESPHome UI'), but there is little wasted text.

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 destructive, no-output-schema tool, the description covers safety ordering, permissions, transport, and failure routing well. The one remaining gap is return/output behavior (the summarising of long output), which is only covered by the full_output schema parameter, not the description.

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 100%, so all five parameters are already documented in the schema. The description's only parameter note ('port' is device address or 'OTA', the default) merely restates the schema, adding no syntax or format detail beyond it. Baseline 3 is appropriate.

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 compound verb and resource: 'Compile and flash firmware to a device over the air.' It also frames the outcome ('This is how you update an ESPHome device'), making its role relative to the compile-only sibling evident without opening a schema.

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 explicit routing: use this for over-the-air updates, and if ESPHome is reported unreachable, call esphome_dashboard_info to diagnose 'rather than telling the user this is unsupported.' That names both the condition and the alternative tool, which is exactly what a routing description should do.

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