edubase_delete_exam_permission

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

The description merely states 'Remove' which aligns with destructiveHint=true, but adds no behavioral details beyond what annotations already provide. It does not explain side effects, error conditions, or the result of removing a non-existent permission.

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 succinct sentence that clearly states the purpose. It is front-loaded and efficient, though it sacrifices helpful details for brevity.

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 presence of an output schema and the operation's destructive nature, the description omits important context such as return format, idempotency (already in annotations but not in description), and error handling. It is incomplete for a delete operation.

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 coverage is 100% with all parameters described. The description does not add any meaning beyond the schema definitions (e.g., 'exam identification string'). 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 'Remove a user permission from an exam.' clearly states the action (remove) and the resource (user permission from an exam). It differentiates this tool from sibling tools like edubase_delete_exam (deletes the entire exam) and edubase_delete_exam_users (removes users from an exam).

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 versus other similar tools (e.g., edubase_delete_exam_users) or any prerequisites (e.g., the permission must exist). It lacks context for appropriate use cases.

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