List user groups

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

Discloses cursor pagination and free-text search across key and name. With no annotations, this adequately describes the read-only nature, though it could add more about return structure.

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?

Two concise sentences with front-loaded purpose and no fluff. Every sentence adds value.

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?

Covers pagination, search, and usage context. Lacks details on return object structure and the include_archived parameter, but sufficient for typical list operations.

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?

Explains the 'search' parameter as free-text across key and name and implies cursor/limit via pagination, but omits the 'include_archived' parameter. With 0% schema coverage, more explicit parameter descriptions would be beneficial.

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?

Clearly states 'List user groups in the current project' with a specific verb and resource. Distinguished from sibling tools like group_create and group_add_member.

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?

Explicitly advises using this tool before group_create to check for existing groups, providing clear guidance on when to use it relative to alternatives.

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