EduBase MCP Server

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

While annotations correctly mark this as destructive and idempotent, the description adds no context about what destruction entails (permanent removal, impact on active connections, or reversibility).

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 two-word description is brief but constitutes under-specification rather than effective conciseness; the sentence fails to earn its place by adding no actionable information beyond the tool name.

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?

Inadequate for a destructive operation with numerous similarly-named sibling tools. The description should clarify the distinction between deleting an integration entity versus deleting its sub-resources (permissions, tags).

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 the 'integration' parameter documented as an 'integration identification string'. The description adds no further semantics, meeting the baseline for high schema coverage.

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 integration' merely restates the tool name (delete/remove synonym) without clarifying what type of integration is being removed or distinguishing from siblings like edubase_delete_integration_permission.

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 tool versus alternatives such as edubase_delete_integration_tag or edubase_delete_integration_permission, nor any prerequisites for deletion.

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