esphome_get_addon_logs

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

No annotations provided, description carries burden but only states it shows last N lines and example content. Missing details like prerequisites, live vs static log, failure conditions.

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?

Two sentences, no fluff, verb and resource front-loaded, efficient for a simple tool.

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?

Adequate for a simple log tool with output schema. Could mention param optionality or behavior for clarity, but not critically lacking.

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 has one param 'lines' with 0% schema description coverage. Description mentions 'last N lines' without explicitly linking to the parameter or explaining its optionality and default.

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?

Description clearly states verb 'Get', resource 'ESPHome add-on log output', and specifics 'compile errors, OTA status, device connections', distinguishing from sibling tools like supervisor_get_addon_logs.

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?

Implies usage for debugging compile errors, OTA, etc., but no explicit when-to-use or alternatives mentioned. Lacks comparisons with other ESPHome tools.

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