eduframe-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers only the word 'Delete'. It does not specify whether this is a hard delete or soft delete, what happens to associated enrollments/elements, or whether the operation is reversible.

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?

While brief at only four words, this represents under-specification rather than efficient conciseness. The single sentence merely restates the tool name and wastes the opportunity to front-load critical behavioral warnings or sibling differentiations.

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 single-parameter operation, the description is inadequate. With no output schema, no annotations, and significant ambiguity regarding sibling tools (delete_program), the description should provide behavioral context and usage guardrails that are completely absent.

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?

The input schema has 100% description coverage ('ID of the program edition to delete'), so the schema adequately documents the parameter. The description adds no supplemental parameter guidance, which is acceptable given the complete schema documentation.

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 program edition' is essentially a tautology that restates the tool name without adding specificity. It fails to distinguish this tool from sibling delete_program, which deletes the entire program rather than a specific edition.

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 is provided on when to use this tool versus delete_program or cancel_program_enrollment. There are no warnings about prerequisites, cascading effects on enrollments, or irreversibility considerations for this destructive operation.

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