ha_get_automation

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. 'Get' implies a read-only operation with no side effects, which is correct. However, it does not disclose potential permissions needed, error behavior (e.g., invalid ID), or any rate limiting. For a simple read operation, this is adequate but could be more transparent.

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, well-structured sentence with no extraneous words. It efficiently conveys the core functionality.

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?

With no output schema, the description should explain what the returned configuration contains. 'Full configuration' is vague; the agent cannot infer the structure or fields. The description also omits error scenarios. For a simple get operation, this is acceptable but not comprehensive.

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 coverage is 100% and the schema already describes the parameter as 'The automation config key/ID (the 'id' field from ha_list_automations)'. The tool description only repeats 'by its ID' without adding new meaning, so it does not significantly enhance understanding 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 'Get' and the resource 'full configuration of an automation', specifying retrieval by ID. It differentiates from sibling tools like ha_create_automation, ha_update_automation, ha_delete_automation, and ha_list_automations by indicating it returns the full configuration for a single automation given an ID.

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 minimal usage guidance. It implicitly suggests that the automation_id should come from ha_list_automations, but does not specify when to use this tool over alternatives (e.g., ha_get_entity for a different context) or any prerequisites or limitations.

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