get_automation

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

No annotations provided. Description states it fetches definition including conditions and actions, but does not disclose side effects, auth requirements, rate limits, or if it's read-only. Adequate but could add more 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?

Single sentence, no waste, front-loaded with key information. Every element earns its place.

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?

No output schema, so description should explain return values. It mentions 'including its conditions and actions array', which helps. However, more detail on the full response structure would be beneficial.

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% with one parameter 'id' described as 'Automation ID'. Description adds no extra meaning beyond schema; it only reiterates 'numeric ID'. Baseline 3 is appropriate as schema does the heavy lifting.

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?

Clearly states it fetches one automation's definition by numeric ID, including conditions and actions. Verb 'Fetch' is specific to the resource 'automation's definition'. Distinguishes from siblings like list_automations (list) and other get_* 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?

No explicit when-to-use or when-not-to-use. No alternatives mentioned. The description implies usage for fetching a single automation by ID, but lacks guidance on when to prefer this over list_automations or other get tools.

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