EduBase MCP Server

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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the safety profile. The description adds no further behavioral context (e.g., what happens if the permission doesn't exist, side effects on event access), but 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?

The description consists of a single, efficient sentence with no redundant words. Every word earns its place by conveying the core action and target.

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 (not shown in detail but indicated), the description appropriately omits return value details. Combined with comprehensive annotations and schema coverage, the description is complete for a straightforward deletion operation, though it could note the idempotent nature for retry clarity.

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?

With 100% schema description coverage ('event identification string', 'user identification string', and the permission enum values), the schema fully documents parameters. The description adds no supplementary semantics, meeting the baseline for well-documented schemas.

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 provides a specific verb ('Remove'), clear target ('user permission'), and scope ('from an event'), precisely distinguishing it from siblings like 'edubase_delete_event_tag' (which removes tags) and 'edubase_post_event_permission' (which adds permissions).

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 offers no guidance on when to use this tool versus alternatives (e.g., when to delete vs. modify permissions), nor does it mention prerequisites like the user needing to have the permission beforehand.

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