list_groups

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('List groups') and does not mention any destructive side effects. However, it does not explicitly state safety or describe edge cases. For a simple list tool, this is adequate but could be more explicit.

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 concise (a few lines), front-loads the purpose, and uses a structured Args section. Every sentence adds value, and there is no redundant or verbose content.

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 (one parameter, output schema exists), the description covers purpose, parameter semantics, usage guidelines, and outcome usage. It also cross-references a sibling tool for further actions, making it self-contained for effective invocation.

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?

With 0% schema description coverage, the description adds meaning by explaining that school_id is the school identifier and instructing to use list_schools to find available IDs. This goes beyond the schema, providing context on how to obtain valid values. It does not elaborate on constraints (e.g., no range), but is sufficient for correct invocation.

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 'List groups at a school with member counts and descriptions,' which clearly identifies the action (list), resource (groups), and the data returned. It also distinguishes itself from siblings like get_group_feed by noting that viewing posts requires a different tool.

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 provides explicit context: when to use (list groups), what not to use for (view posts), how to use the parameter (school_id found via list_schools), and how to apply results (use group_id with get_group_feed). This fully guides the agent on appropriate usage.

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