edubase_delete_exam_users

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive nature is disclosed. The description adds no further behavioral context (e.g., whether removal is permanent, cascades to results, or generates notifications), but it does not contradict the annotations.

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?

Single sentence with no filler; the core action and parameter basis are both stated. Perfectly sized for the simple operation.

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?

The tool is a simple two-parameter deletion operation with full schema coverage and annotations indicating destructive and idempotent behavior. The description, combined with the schema and annotations, gives an agent everything needed to invoke it correctly; no output schema is required.

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?

The schema covers 100% of parameters with descriptions: 'exam identification string' and 'comma-separated list of user identification strings'. The description repeats the notion of 'user identification strings' but adds no new semantics beyond what the schema already provides.

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 'Remove users from an exam by their user identification strings' uses a specific verb ('remove') and resource ('exam users'), and clarifies the selector. This clearly distinguishes it from sibling tools like edubase_delete_exam (deleting the whole exam) or edubase_post_exam_users (adding users).

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 usage for removing users from an exam, but it does not explicitly state when to prefer this tool over alternatives such as edubase_post_exam_users (adding users) or edubase_delete_exam (deleting the entire exam). The context of the name and sibling list makes the intended use inferable, but the description itself provides no explicit guidance or exclusions.

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