esphome_compile

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

With no annotations, the description must disclose behavior, but it only says 'Trigger OTA compilation' without explaining side effects, whether it performs a full OTA update, or if it requires network connectivity. The term 'OTA compilation' is ambiguous and lacks detail about the actual action's impact.

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, concise sentence with no filler. It is front-loaded with the action verb, and every word contributes to the stated purpose. Length is appropriate for the tool's apparent simplicity.

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?

Without annotations or an output schema, the description should explain return values, prerequisites, and side effects. It does none of these. The tool triggers a compilation, but the description omits what the agent can expect (e.g., success/failure output, async behavior) and under what conditions it is valid.

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?

The input schema already provides full descriptions for both parameters (device_id and esphome_device). The description adds no additional meaning or context about how these parameters relate to the compilation process. Baseline 3 applies since schema coverage is 100%.

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 'Trigger OTA compilation for an ESPHome device' uses a specific verb (Trigger) and resource (OTA compilation), clearly distinguishing it from sibling tools like esphome_get_states or esphome_call_service. It unambiguously identifies the operation's focus.

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. It does not mention prerequisites (e.g., device must be online), nor does it exclude scenarios like using esphome_call_service for running services. The description leaves usage entirely implicit.

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