EduBase MCP Server

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

Annotations correctly identify this as destructive and idempotent, but the description adds no behavioral context beyond what the annotations provide. It fails to mention what happens to nested resources (members, courses, exams), whether deletion is permanent, or required authorization levels for such a destructive 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?

The description is extremely brief (two words), which prevents bloat, but this brevity fails to earn its place by adding value. It is front-loaded but wastes the opportunity to provide necessary context for a destructive operation on a primary resource.

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?

For a destructive operation on a top-level organizational entity with cascading implications, the description is inadequate. No output schema exists, yet the description does not indicate what successful deletion returns or whether partial deletion is possible.

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 (the 'organization' parameter is documented as 'organization identification string'), the description does not need to compensate for missing schema documentation. The description mentions no parameters, which is acceptable given the schema carries the full semantic load.

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 organization' is a tautology that restates the tool name (edubase_delete_organization). While it confirms the action and resource, it fails to distinguish this tool from siblings like edubase_delete_organization_members or edubase_delete_organization_tag, which is critical given the 40+ sibling deletion tools available.

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. Given the presence of numerous sibling tools for deleting organization sub-resources (members, permissions, tags, webhooks), the description should explicitly state this deletes the entire organization entity and suggest when to use the more granular deletion tools instead.

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