esphome_get_logs

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

Without annotations, the description is the sole source of behavioral information. It merely states the action 'Get logs' without describing the output format, whether logs are streamed or returned as a snapshot, or any required access permissions. This is a minimal disclosure that leaves significant ambiguity about the tool's behavior.

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 short sentence that is appropriately concise and front-loaded, with no unnecessary words. It clearly states the core action and resource in a compact format.

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 simple two-parameter tool with no output schema, the description provides only the basic purpose. It does not explain what kind of logs are returned, how they are presented, or any limitations. This lack of detail leaves the agent uncertain about the tool's actual output, making it incomplete for reliable invocation.

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 already provides descriptions for both parameters (device_id and esphome_device) with 100% coverage, so the baseline is 3. The description adds no additional meaning about parameter usage, but the schema is sufficient to understand the required inputs.

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 uses the specific verb 'Get' and resource 'logs from an ESPHome device', which clearly states the tool's function. However, it does not distinguish this from other log-retrieval tools like switch_show_logs or qnap_get_logs, though the ESPHome context is evident from the name and sibling tools.

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 description provides no guidance on when to use this tool versus alternatives such as esphome_get_states or other device-specific log tools. There is no mention of prerequisites, scenarios, or situations where another tool might be more appropriate.

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