PupilsGetList

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 clear. The description adds that search, filtering, and pagination are supported, but it does not disclose behavioral details such as default page size, ordering, or how OnlyUpdated and OnlyUnchanged interact.

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 a single front-loaded sentence with no wasted words. It conveys the core operation and the main parameter categories efficiently.

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 list endpoint with eight parameters and no output schema, this description is minimally viable but thin. The parameter names are mostly self-explanatory and annotations cover the read-only behavior, yet the description omits details about pagination behavior, filter semantics, and the response shape.

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%, which sets the baseline at 3. The description groups parameters into 'search', 'filters', and 'pagination', adding a little semantic structure, but it does not explain individual parameters beyond what their names already convey.

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 clearly states the verb 'List', the resource 'pupils', and the core capabilities: search, filters, and pagination. It does not explicitly differentiate from the sibling PupilsGetCursorList, but the basic purpose is unmistakable.

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 when to use the tool—when a filtered, paginated list of pupils is needed—but it gives no explicit guidance about alternatives such as PupilsGetCursorList or PupilsGetDetail. An agent would have to infer the selection criteria from tool names.

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