list_groups

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool lists groups with active post counts and descriptions, implying a read-only operation, but does not mention pagination, sorting, or any side effects. It adds some context (the relationship to get_group_feed) but lacks explicit statements about read-only guarantees or edge cases.

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 short and front-loaded with the primary purpose. It then gives a useful next-step hint and a parameter explanation, all in a compact structure. No superfluous text; 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?

Given the presence of an output schema (which defines return shape), the description covers the essential call context: required parameter, how to obtain it, and how to follow up. It doesn't mention limitations like pagination or error handling, but for a simple list tool with one parameter, it is adequately complete.

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 description coverage is 0%, so the description must compensate. It explains that school_id refers to a school ID and directs the user to list_schools to find valid IDs, adding meaning beyond the raw integer type. This is sufficient for the single required parameter.

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 states a specific action ('List groups at a school') with a clear object (groups) and key attributes (active post counts and descriptions). It differentiates from siblings like list_class_students or list_schools by being group-specific, so an agent can immediately recognize its unique purpose.

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?

Provides explicit guidance on prerequisite steps: how to obtain school_id via list_schools, and how to proceed to view posts using get_group_feed with matching school_id and group_id. It names the relevant sibling and the condition for switching, though it doesn't explicitly state when not to use this tool (e.g., if you need a single group's details).

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