listAutomations

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

With no annotations provided, the description carries the burden. It discloses access restrictions and the Automations 2.0 requirement, but does not describe return format, pagination behavior, or error cases. The word 'List' implies a read-only operation, but without explicit safety statements, transparency is partial.

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 short sentences, front-loaded with purpose and then necessary access constraints. No redundant phrasing, every sentence provides substantive information.

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?

For a simple list tool with two optional params and no output schema, the description is adequate but not complete. It states the purpose and access restrictions but does not mention what the response looks like or how pagination behaves beyond the schema's parameter descriptions. It leaves out potential defaults or result structure.

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 already provides descriptions for both parameters (limit and offset) with 100% coverage. The description adds no additional meaning about these parameters, so it does not exceed the baseline for schema-suffcient cases.

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 'List all Automations 2.0 automations,' using a specific verb ('List') and resource ('Automations 2.0 automations'). This distinguishes it from sibling tools like 'getAutomation' (single) and 'listAutomationsPeople' (people within automations).

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?

Provides clear context on prerequisites: the 'Restricted - Registered Systems Only' requirement (FUB_SYSTEM + FUB_SYSTEM_KEY) and the need for the account to be on Automations 2.0. However, it does not explicitly mention alternatives or when to use this tool versus others like getAutomation.

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