edubase_delete_user_classes

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

Annotations indicate destructiveHint: true and idempotentHint: true, so the description correctly implies a destructive action. The description aligns with annotations (no contradiction). However, it does not add behavioral detail beyond what annotations already convey, such as whether the tool permanently deletes data or just removes associations.

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, concise sentence with no fluff. It is front-loaded with the action and resource. Minor improvement would be to clarify the relationship between the two parameters.

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?

Given the tool's moderate complexity (2 required params, no output schema, no nested objects), the description is minimally adequate. It tells what it does but not the effect on the system, prerequisites (e.g., user must be in class), or side effects. Sibling tools exist for adding users to classes, so cross-reference would help.

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% for both parameters ('user identification string', 'comma-separated list of class identification strings'). The description adds no extra meaning beyond what the schema provides, so 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 clearly states the verb 'remove' and the resource 'user from class(es)'. It distinguishes from sibling tools like edubase_delete_user (removes the user entirely) and edubase_post_user_classes (adds user to classes). However, it could be more specific by stating it removes the user's membership, not just the user.

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 provides no guidance on when to use this tool vs alternatives. Among siblings, there is edubase_post_user_classes (add) and edubase_delete_class_members (remove from a single class), which are related. No mention of when to prefer this over those or vice versa.

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