groups_list

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

The description is minimal and does not disclose behavioral traits beyond what is obvious from 'list'. It does not mention read-only status, pagination, rate limits, or required permissions. With no annotations, the description carries full burden, and it falls short.

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 a single, front-loaded sentence with no fluff. It states the action first and then the optional filters, making it easy to scan and understand.

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?

The description is adequate for a simple list operation but lacks details on return format, pagination behavior, or whether query and userKey can be combined. The schema covers maxResults auto-pagination, but the description does not reinforce it, and there is no output schema to explain the response 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 description adds meaningful context for query (with an example 'email:sales*') and userKey (listing groups a user belongs to), which compensates for the lack of schema description on the query parameter. The maxResults parameter is left to the schema, but schema coverage is 67% and the extra context is valuable.

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 groups' with a specific verb and resource, and it distinguishes the tool from siblings like groups_get (specific group) and groups_list_members (list members) by focusing on the list operation. However, it does not explicitly name alternative tools for different use cases.

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 implies when to use the tool by showing optional filters (query, userKey) and gives an example, but it does not explicitly state when to use alternatives or exclude other tools. There is no mention of 'use groups_get for a single group' or similar guidance.

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