eduframe-mcp

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

While annotations correctly indicate the operation is destructive and idempotent, the description adds no behavioral context beyond what the name and annotations already provide (e.g., whether deletion is permanent, cascades to student records, or requires specific 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 extremely brief (3 words), which is appropriate for a single-parameter tool, but the content is uninformative (restates the name) rather than being efficiently packed with useful context.

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?

Given the simple arity (1 parameter), complete schema coverage, and comprehensive annotations covering safety profiles, the description is minimally viable, though it could specify the domain concept (academic grade/score) and deletion permanence.

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 ('ID of the grade to delete'), the description appropriately relies on the schema to document the parameter, meeting the baseline expectation when structured documentation is complete.

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 grade' is a tautology that restates the function name (delete_grade) without adding specificity about what constitutes a 'grade' in this educational context or distinguishing from siblings like update_grade or create_grade.

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 update_grade (for modifying vs removing), prerequisites for deletion, or consequences for related enrollments/records.

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