acedatacloud_list_services

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

With no annotations, the description carries full burden. It states returns 'count + items' but does not disclose pagination behavior or limits despite the `limit` parameter. It is straightforward but lacks deeper 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?

The description is concise with three sentences, no redundancy, and front-loaded with the primary purpose. Every sentence provides value without extra fluff.

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 tool's simplicity (2 params, no required parameters, output schema exists), the description fully covers what the agent needs: the action, what it returns, and how to use the `search` parameter. No gaps identified.

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 detailed descriptions for both `limit` and `search`. The description does not add new parameter information beyond the schema; it only reiterates the search purpose. Baseline 3 is appropriate.

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 the tool lists services, defines what a service is, and distinguishes from 'search' functionality. It uses the verb 'list' with a specific resource 'services', making the purpose evident among many sibling list 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?

The description explicitly tells when to use search ('Use `search` to find one by alias/title'), guiding the agent on when this tool is appropriate vs the search parameter. It lacks explicit exclusion of other siblings but provides clear context.

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