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 discloses the critical requirement for administrator privileges, which is a significant behavioral trait that will affect invocation success. The verb 'list' implies a read-only operation, but this is not explicitly stated; however, for a simple list tool, this is adequate.

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 that conveys both purpose and access requirements without any wasted words. It is concise and well-structured, earning a top score.

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?

Given the tool's simplicity (0 parameters, no nested objects, output schema provided), the description is sufficiently complete. It states what the tool does and the access requirement. The presence of an output schema means return values do not need to be described, and no other context is missing.

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, and the schema confirms this. The baseline for 0 parameters is 4. The description adds useful context by specifying that the listing is at the instance level, clarifying the scope, though it does not need to explain parameter syntax since there are none.

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 uses the specific verb 'list' and identifies the resource as 'user groups of the instance,' clearly distinguishing it from sibling tools like get_group (which retrieves a single group) or create_group (which creates one). The scope is explicit, making the purpose 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?

The description states a key prerequisite (administrator privileges) but does not explicitly mention when to use this tool versus alternatives like get_group or create_group. The usage context is implied by the verb 'list' and the instance-wide scope, but no direct exclusions or alternative suggestions are provided.

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