edubase_delete_event_permission

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

The annotations already indicate destructiveHint=true and idempotentHint=true. The description adds the specific action but does not provide additional behavioral context such as side effects, authentication needs, or rate limits, beyond what annotations convey.

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 that efficiently states the purpose. However, it could potentially include more context without becoming verbose, so it is slightly above average but not exceptional.

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 existence of an output schema and rich annotations, the description provides adequate high-level information. However, it lacks details on side effects (e.g., cascading permission removal) or prerequisites (e.g., user must have existing permission), leaving some gaps in completeness.

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 input schema fully describes all three parameters (event, user, permission) with 100% coverage. The description does not elaborate on parameter values or their semantics, so it adds no meaningful information beyond the schema.

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 event' clearly states the action (Remove) and the resource (user permission on an event). It distinguishes this tool from sibling delete_permission tools for other entities (e.g., class, exam) by specifying 'from an event'.

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 event permissions but provides no explicit guidance on when to use this tool over alternatives. There is no mention of when not to use it or references to related permission tools like post_event_permission or get_event_permission.

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