get_agent_groups

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

No annotations are present, so the description carries the full burden. It only states the action ('List all agent groups') without disclosing behavior like pagination semantics, default page size, sorting, or potential rate limits. The args section mentions 'page' and 'per_page' but does not clarify whether 'all' means all pages or a single page.

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 and front-loaded with the main action. However, the 'Args' section duplicates information already present in the input schema, making it slightly redundant. Still, it is appropriately sized and has no unnecessary 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 simple list tool with pagination and an output schema (presumably an array of agent groups), the description is fairly complete. However, the use of 'all' is ambiguous given pagination, and there is no mention of sorting or whether the output includes pagination metadata. It does not explicitly distinguish from related list tools.

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 restates the parameter names as 'Page number' and 'Results per page', which adds minimal meaning beyond the schema's existing titles ('Page' and 'Per Page') and default values. With 0% schema description coverage, the description does not sufficiently compensate for the lack of parameter detail.

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 'List all agent groups' uses a specific verb ('List') and clearly identifies the resource ('agent groups'). It distinguishes from sibling tools like 'get_agent_group_by_id' (single group) and 'get_requester_groups' (different resource type).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that 'get_agent_group_by_id' retrieves a single group, nor does it note any filtering capabilities. There is no 'when to use' or 'when not to use' context.

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