list_student_groups

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

Annotations already declare this as read-only, idempotent, and non-destructive, but the description adds no behavioral context beyond that—no pagination behavior, filter semantics, or default ordering. It does not contradict the annotations, so it is not a 1, but it contributes nothing beyond the schema.

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 three words long and under-specified. It is concise in word count but not appropriately sized for a tool with four parameters and a large sibling set; there is meaningful content missing.

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?

Despite the annotations and output schema covering safety and return shape, the description does not explain what a 'student group' is, how filters interact, or how this differs from other list tools. The context is insufficient for an agent to confidently choose and invoke this tool.

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 100%, so all four parameters (limit, offset, subject_id, classroom_id) are already documented. The description itself adds no parameter meaning, but the baseline of 3 applies because the schema carries the load.

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 'List Student Groups' is essentially the tool name rewritten with spaces, adding no scope, filtering intent, or differentiation from the many sibling list_* tools. It is a tautology rather than a substantive definition.

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?

There is no guidance on when to use this tool versus alternatives like get_student_group, list_students, or list_classrooms. No conditions, exclusions, or context are provided.

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