group.list

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

No annotations are provided, so the description carries the entire burden of behavioral disclosure. It discloses nothing about whether the operation is read-only, what a 'group' is, whether pagination applies, or what is returned — a critical gap for a list operation with zero structured support.

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?

It is short, but brevity here is under-specification rather than conciseness: the single fragment is grammatically incomplete and front-loads no actionable information. It earns its place only by being non-empty.

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 schema is a bare empty object with no output schema and no annotations, so the description is the only source of meaning — and it fails to define what a group is or what listing returns. For a zero-parameter tool this is not complex, but the description still leaves the agent unable to predict behavior.

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 there is no parameter meaning to convey. Baseline 4 applies per the rubric; nothing in the description 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 text 'The groups profiles are labelled with.' is a sentence fragment that never states a verb or what the tool actually does. One can infer it relates to listing groups used to label profiles, but the agent must reconstruct that from the name group.list plus guesswork, and it does not distinguish itself from siblings like group.create or group.delete.

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 conditions, and no reference to alternatives such as group.create, group.delete, or profile.list. The agent is given no basis for choosing this tool.

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