list_automations

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves automations with specific fields, implying a read-only operation. However, it does not disclose whether disabled automations are included, rate limits, or permissions required, leaving gaps in behavioral context.

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 relatively short and front-loaded with the purpose. It includes a 'Returns' section and example, but could be slightly more concise by removing redundant phrasing like 'A list of automation dictionaries, each containing'.

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?

Given the tool's simplicity (0 params, no nested objects), the description is complete. It specifies the return fields and provides an example. An output schema exists, so explicit return value documentation is not necessary.

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 tool has no parameters (schema coverage 100%), so the description does not need to add parameter semantics. Baseline for 0 params is 4, and the description adequately covers the absence of parameters.

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 'Get a list of all automations from Home Assistant', specifying the verb and resource. It distinguishes from sibling tools like 'create_or_update_automation' and 'list_entities' by focusing on automations and their specific fields.

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. It does not mention filtering, prerequisites, or exclusions, leaving the agent without context for selection among siblings like 'list_entities' or 'entity_action'.

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