list_automations

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

No annotations provided, but description informs that automations run hourly and lists all without filtering. It doesn't cover auth or rate limits, but for a read-only list tool, the behavioral traits are sufficiently clear.

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 with no fluff: main action first, then example, then distinction, then usage purpose. Every sentence adds value.

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 simple tool with 2 params and no output schema, description adequately explains what automations are, how they differ from triggers, and why to use this tool. Missing return format, but not critical for a list tool.

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%, so baseline 3. Description does not add further meaning to 'page' or 'per_page' parameters beyond what schema already provides.

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 'List ALL automations' and elaborates that these are time-based rules that run hourly, with an example. It distinguishes from triggers by noting scheduling vs. events.

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?

States 'Use this to audit existing time-based workflows' and contrasts with triggers, helping the agent decide when to use this vs. list_triggers or create_automation.

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