eduframe-mcp

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

No annotations are present, so the description carries the full burden. It states the destructive action but omits critical behavioral details: whether deletion is permanent or soft, what happens to related planning_attendees (per sibling tools), or required permissions.

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 appropriately brief at three words, but the single sentence fails to earn its place by adding value beyond the tool name. It is front-loaded but vacuous.

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 with no output schema or annotations, the description is inadequate. It lacks warnings about cascading effects on related entities (planning attendees, teachers) or error conditions (e.g., attempting to delete non-existent events).

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?

Schema coverage is 100% with the 'id' parameter fully documented as 'ID of the planning event to delete'. The description adds no additional parameter context, 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 'Delete a planning event' is a tautology that restates the tool name without adding specificity. It fails to distinguish 'planning events' from similar sibling resources like 'meetings' or 'planned courses', or clarify what constitutes a planning event in this domain.

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 (e.g., cancel_planned_course), prerequisites (such as checking event existence via get_planning_event), or whether the event must be in a specific state before deletion.

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