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 none. It does not clarify whether cancellation is reversible, if it triggers refunds, affects associated enrollments/invoices, or requires specific permissions. For a mutation operation, this omission is significant.

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 (3 words) and front-loaded. While efficient in word count, it errs toward under-specification rather than optimal information density. Structure is simple and direct.

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 in a complex domain (evidenced by 100+ sibling tools including invoicing and enrollment management), the description is inadequate. It should explain cancellation semantics, side effects on related records, and output behavior, especially absent annotations or output schema.

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 parameter already documented as 'ID of the order'. The description adds no additional semantic context about the ID format or where to obtain it, but baseline 3 is appropriate given the schema's completeness.

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 'Cancel an order' is essentially a tautology that restates the tool name. While it identifies the verb (cancel) and resource (order), it fails to distinguish from sibling cancellation tools like cancel_enrollment, cancel_planned_course, or cancel_program_enrollment, leaving ambiguity about which entity type to cancel.

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 approve_order, deny_order, or delete operations. Given the complex domain with orders potentially linked to enrollments and invoices, the lack of usage constraints or prerequisites (e.g., 'only cancel pending orders') creates selection risk.

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