listGroups

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

With no annotations, the description itself is the only source of behavioral information. It only says 'List all groups' and fails to disclose potential side effects, pagination, permissions, or return format. This leaves the agent uncertain about the operation's behavior.

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 concise sentence, easy to parse and front-loaded. It is not bloated, though it may be too terse for a complete understanding.

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 lacks details on return values or response structure, and with no output schema, the agent cannot anticipate what the tool returns. For a list operation, this is a notable gap, though the zero-parameter interface keeps complexity low.

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 accepts no parameters, so the schema fully covers the input surface. The description adds nothing about parameters because there are none; the baseline of 4 applies.

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?

Clearly states it lists all groups, using the verb 'list' and the resource 'groups'. It doesn't elaborate on scope or differentiate from similar list tools like listTeams or listRoundRobinGroups, but the meaning is unambiguous.

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 no guidance on when to use this tool versus alternatives. It simply states the action with no mention of prerequisites, typical use cases, or exclusions.

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