GroupClassPupilsDelete

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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description reinforces this with a warning. It adds meaningful context by explaining the exact effect ('unlinks the pupil') and the requirement for client-side approval.

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 two concise sentences: the action is front-loaded, and the warning is separate and prominent. There is no filler or redundant restating of the tool name.

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 two-parameter destructive operation, the description covers the action, the destructive nature, the specific unlinking effect, and the approval requirement. It does not mention side effects or when not to use it, but the annotations and clear sibling names cover most of the remaining context.

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%, but each parameter description is only 'integer (required),' adding no real meaning. The tool description contextualizes classId and pupilId through 'remove a pupil from a group class,' but does not elaborate on their roles beyond their self-explanatory names.

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 opens with a specific verb and resource: 'Remove a pupil from a group class.' This directly states the operation and distinguishes it from sibling tools like GroupClassPupilsAdd and GroupClassPupilsGetList.

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 implied clearly by the action and object, but there is no explicit guidance on when to use this versus the sibling add/list tools, nor any mention of prerequisites such as the pupil currently being enrolled.

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