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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no mention of ordering, pagination, whether membership is included, or what a "group" represents in this API — and does not contradict the annotations.

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?

A single four-word sentence with zero waste and the verb front-loaded. It is appropriately sized for a zero-parameter tool, though the extreme brevity leaves no room for any orienting context.

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 output schema and annotations cover return shape and safety, and with no parameters there is little an agent must know to invoke it correctly. Still, the description never clarifies what a "group" is in this email/blog-oriented API (contact group vs. permission group) or how many results to expect, which is the main residual ambiguity.

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 zero parameters and the schema is a closed empty object, so there are no parameter semantics to explain. Baseline 4 applies since the description cannot and need not add parameter detail. The word "all" usefully confirms there are no filter arguments.

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?

"List all groups" gives a verb (list) and resource (groups) with an implied full-collection scope, so the basic action is clear. However, it is essentially a restatement of the name/title and does nothing to distinguish it from sibling group tools such as create_group, add_group_members, and remove_group_members.

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 statement of when to use this tool versus the other group-related siblings, nor any prerequisites or exclusions. The agent must infer that this is the read-only enumeration counterpart to create_group and the membership tools.

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