list_groups

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

No annotations are provided, so the description carries the full burden. It only says 'Get Groups List' and discloses no behavioral traits such as read-only nature, pagination, rate limits, or authorization requirements. The agent gets no additional insight beyond the tool name.

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 extremely short, but this is under-specification rather than genuine conciseness. 'Get Groups List' is essentially a label that restates the tool name, providing no substantive information to the agent.

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?

Despite the tool's low complexity (0 params, no output schema), the description lacks essential context such as the scope of the group list and how it relates to other group-related tools. It barely covers the basic purpose and leaves the agent to infer semantics from the name.

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 has zero parameters, so the description doesn't need to add parameter detail. The baseline of 4 is appropriate because there are no parameters to clarify or document.

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 'Get Groups List' states a verb and resource, but it merely rephrases the tool name 'list_groups' without adding specificity or scope. It doesn't differentiate from sibling tools like get_groups_group_id, which retrieves a single group.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that this lists all groups while get_groups_group_id fetches a specific group, nor does it provide any context about use cases or prerequisites.

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