EduBase MCP Server

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds minimal behavioral context ('previously generated' implies the link must exist), but does not explain the immediate effect (invalidation), side effects (logged out users?), or reversibility despite the sensitive security nature of the operation.

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?

Single sentence with zero redundancy. Every word earns its place—'previously generated' establishes the required state, 'login link' specifies the exact resource, and 'Delete' states the action. Appropriately front-loaded for its length.

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 annotations covering safety hints and schema covering parameters, the description provides the minimum viable context. However, for a destructive authentication operation, it lacks explanation of what 'delete' means functionally (immediate invalidation vs. scheduled cleanup) and whether this affects other user sessions or links.

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?

Input schema has 100% description coverage with clear definitions ('user identification string', 'generated login link to be invalidated'). The description does not add parameter-specific semantics, but with complete schema coverage, 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 action (Delete) and resource (previously generated login link), distinguishing it from siblings like edubase_delete_user that operate on the user account itself. However, it misses the opportunity to explicitly clarify that this invalidates an authentication credential rather than removing 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?

No guidance provided on when to use this versus alternatives (e.g., edubase_delete_user for full account removal), nor prerequisites such as requiring the link to exist or whether this affects currently active sessions.

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