listRoundRobinGroups

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

The description merely states 'list' implying a read-only operation, but lacks details about sorting, filtering, pagination, or return format. Without annotations, the description should provide more behavioral context, which is missing.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose.

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 simple list tool with no parameters and no output schema, the description is adequate but could be improved by mentioning return structure or typical fields (e.g., 'Returns group IDs and names'). Completeness is acceptable but minimal.

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 input schema has no parameters (100% coverage) and the description adds no parameter info, which is appropriate since none exist. Baseline for zero-parameter tools is 4, and the description meets this without needing to add extra meaning.

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 'List round robin groups' clearly states the action (list) and the resource (round robin groups). It effectively distinguishes from sibling tool 'listGroups' which likely lists all groups. The verb+resource pattern is specific and 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?

No guidance is provided on when to use this tool versus alternatives like 'listGroups' or other list tools. The description lacks context for decision-making, such as prerequisites or typical use cases.

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