GroupClassPupilsGetList

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the pagination behavior and group-class scoping; it does not explain pagination defaults, ordering, or empty-result behavior, so it adds some but not rich behavioral context.

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?

One front-loaded sentence states the action and resource, and the parenthetical '(paginated)' adds the single most important behavioral fact with zero wasted words.

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 operation with one required ID and two pagination parameters, the description plus annotations and schema cover what an agent needs to select and invoke the tool correctly. It does not specify the exact return shape, but the tool's name and 'List pupils' communicate the result type sufficiently.

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%, so the schema carries the parameter documentation. The description's 'paginated' hints at the role of pageSkip and pageTake, but it does not add semantic detail beyond that; the baseline 3 is appropriate.

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 pupils') and target resource ('group class'), and notes pagination. This clearly distinguishes it from sibling mutations like GroupClassPupilsAdd/Delete and from GroupClassesGetList, which lists classes rather than pupils.

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 intended use is evident from the direct phrasing: retrieve pupils belonging to a group class, using pagination for large result sets. It does not explicitly enumerate sibling alternatives or exclusions, but the domain context makes when to call it clear.

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