esphome_list_devices

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

With no annotations, the description must disclose behavioral traits itself. It fails to explain why a device_id is required for a 'list all' operation, nor does it mention authentication, pagination, output format, or side effects. This is a significant transparency gap.

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 that is easy to read. It would earn a 5 if not for the misleading 'all' qualifier that contradicts the schema.

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 tool with no annotations, no output schema, and a potentially mystifying required parameter, the description is incomplete. It fails to explain the tool's scope, use cases, or behavior, leaving the agent with insufficient information to invoke it 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?

The schema provides 100% parameter coverage with the description 'ESPHome controller device ID', so the baseline is 3. However, the tool description's 'list all' phrasing conflicts with the required parameter, adding confusion rather than clarity. The description adds no further meaning beyond the schema.

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 verb 'List' and the resource 'ESPHome devices', but it claims to list 'all' devices while the input schema requires a specific device_id. This inconsistency undermines the clarity of what the tool actually does, making it less distinct from sibling tools like espconnect_list_devices or iot_list_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?

There is no guidance on when to use this tool versus alternatives. Given the many similar list devices tools (e.g., sonoff_list_devices, tuya_list_devices, tb_list_devices), the description offers no selection criteria or context, leaving the agent without clear direction.

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