list_automations

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

No annotations provided, so description carries full burden. It implies read-only behavior but does not disclose whether it only returns active automations or all automations, nor any other behavioral traits like pagination or data format.

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?

Extremely concise: two sentences, no wasted words. First sentence states the core purpose clearly, second adds a usage hint. Structure is front-loaded and efficient.

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, and description is brief. It covers the basic purpose and a filter hint, but lacks details about response structure, behavior when event_id is omitted, or any constraints (e.g., only active automations). For a simple list tool, it is minimally adequate.

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. The description adds context that filtering by event_id reveals active automations, which goes beyond the schema's 'Filtra por evento (opcional)' – adding practical meaning.

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 states it lists automations for an event, which is a specific verb+resource. It distinguishes from siblings like create_automation and delete_automation, but does not explicitly mention whether it lists all automations or only for a specific event when no filter is provided.

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 filtering by event_id to see active automations, but lacks guidance on when to use this tool versus alternatives like get_automation, or when not to use it.

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