List tester groups

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read only' in the description is largely redundant. What does add value is the disclosure of return shape (member counts, per-group installable projects), which matters because no output schema exists. It still says nothing about ordering, pagination, or behavior on an empty workspace.

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 content is front-loaded and short, which is right for a zero-argument list tool. However, it is written as three clipped fragments, and the final 'Team.' token adds no discernible meaning while consuming space that could have held real guidance.

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 no-parameter, no-output-schema read tool, describing the returned fields is the essential job, and the description does that. It is still thin on what an agent would want before calling it, such as grouping/ordering of results and whether groups with no testers appear, and the 'Team.' fragment suggests omitted context.

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, so the baseline is 4 and there is no parameter meaning for the description to carry. Nothing in the text misleads about inputs.

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 names the resource unambiguously (tester groups of the workspace) and lists the payload an agent gets back: member counts and installable projects. The listing verb is implicit rather than stated, and it does not explicitly distinguish itself from the sibling list_testers, but the noun phrase is specific enough to select on.

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 when-to-use guidance, no prerequisites, and no pointer to a related or alternative tool such as list_testers. The trailing words 'Read only. Team.' do not function as usage direction; 'Team.' is an unexplained fragment an agent cannot act on.

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