list_groups

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

No annotations are provided, so the description carries the behavioral burden. It does disclose 'Read-only' and the underlying SOAP operation, which is useful. It does not mention pagination, result ordering, or size limits - relevant gaps for a list call, though modest for a zero-parameter read.

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?

Three short sentences, front-loaded with the core action, then the usage hook, then the read-only/source note. No filler.

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 no-parameter, read-only list tool with no output schema and no annotations, the description covers purpose, sequencing, safety profile, and the shape of the return (ids). Minor omissions around pagination or the group/list distinction keep it from a 5.

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 tool takes no parameters, so the baseline is 4. The description adds meaning by stating the output includes ids, which is the key payload an agent needs to chain into other calls.

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?

States a specific verb (List) and resource (mailing lists on the account) and even hints at the returned content ('with their ids'). However, it does not differentiate itself from the sibling 'get_groups', which sounds like it covers similar ground, so an agent cannot fully disambiguate from the description alone.

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?

'Start here - most other calls take a group' gives explicit sequencing guidance: this is the entry point whose ids feed other calls. It stops short of naming which alternatives to avoid or when not to use it, but the routing intent is clear.

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