get_user_groups

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds beyond this by specifying sorting order (most recent first), pagination, and a default limit of 20 users per page. No contradictions with annotations.

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 very concise, with the key purpose stated upfront ('Get all user groups') followed by essential behavioral details in two sentences. No unnecessary information or repetition.

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 read-only list tool with one optional parameter, the description covers the core functionality (returns all groups), ordering, pagination, and default limit. It lacks explicit mention of output structure, but no output schema exists, so the description is adequate.

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?

Schema coverage is 100%, describing the page parameter. The description adds meaning by stating the default page limit (20 users), which is not in the schema, and implicitly explains the effect of pagination on the results.

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 explicitly states 'Get all user groups' and specifies that it returns all user groups of the school, sorted by recency, which clearly distinguishes it from siblings like get_user_group (single group) and get_user_groups_that_user_is_member (filtered by user).

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 implies usage for retrieving all user groups, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_user_group for a specific group or get_user_groups_that_user_is_member for user-specific groups). No exclusions or context are mentioned.

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