get_advance_automation

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

With no annotations, the description fully discloses behavior: it returns JSON with detail, including quirks like Quirk 21 for schedule modes and port resolution from bitmasks. It also specifies the failure response format. This provides comprehensive behavioral transparency.

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 detailed but well-structured with Args, Returns, and specific formatting details. Every sentence adds value, though it is somewhat lengthy. It could be slightly more concise, but the level of detail justifies the length.

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 output schema exists, the description goes beyond by explaining return fields in detail, including edge cases like schedule_note and error responses. It covers everything needed for an agent to invoke and interpret the result 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 input schema has 0% description coverage, but the description explains each parameter: device_id is 'The AC Infinity device code (from discover_devices)' and automation_id is 'the automation_id from list_advance_automations.' This adds necessary context beyond bare parameter names.

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 starts with 'Get full detail for a single Advance Automation by ID,' using a specific verb and resource. It clearly distinguishes from siblings like list_advance_automations and create/delete/disable/enable, which are separate operations.

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 mentions prerequisites ('device_id from discover_devices' and 'automation_id from list_advance_automations'), guiding the agent on when to use this tool. It does not explicitly state when not to use it or list alternatives, but the context is clear enough for an AI agent.

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