edubase_delete_exam_permission

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

The annotations already declare destructiveHint=true and idempotentHint=true. The description adds little beyond that. It does not clarify what happens to dependents, whether the user must still exist, or that the operation is irreversible. For a destructive tool, more behavioral context would be valuable, but the annotation covers the basic intent.

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 sentence of only 5 words, perfectly front-loaded, and contains zero filler. Every word serves a purpose: 'Remove' conveys the action, 'user permission' the target, and 'from an exam' the scope. This is maximally concise while still being complete.

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?

With 100% schema coverage, an output schema present, and annotations clarifying destructive/idempotent behavior, the description is adequate for a straightforward delete operation. It could optionally mention that this mirrors a sibling 'post_exam_permission' or that the permission value must match an existing assignment, but the essential information is conveyed.

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%, with each parameter having clear descriptions. The description verb 'Remove' adds the context that this is a deletion operation, which is consistent with the parameters (exam, user, permission). No additional parameter semantics are needed beyond what the schema 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 uses the specific verb 'Remove' and clearly identifies the resource as 'a user permission from an exam.' This directly distinguishes it from siblings like 'edubase_post_exam_permission' (add permission) and 'edubase_get_exam_permission' (list permissions), making the tool's purpose 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 tool involves removing a permission, and the destructiveHint annotation implicitly warns about potential impact. However, the description does not explicitly state when to use this tool over alternatives (e.g., editing permissions via post_exam_permission) or any prerequisites (like the exam must exist). The agent gets the basic action but lacks context on appropriate invocation.

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