eduframe-mcp

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

Annotations already establish the operation is destructive and idempotent. The description adds no behavioral context beyond this, failing to disclose what happens to dependent entities (e.g., planned courses using this location), whether deletion is permanent, or permission requirements.

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 a single, brief sentence that is front-loaded, but it is underspecified rather than appropriately concise. It lacks the necessary detail for a destructive operation while not being verbose.

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 this is a destructive operation (destructiveHint: true) with no output schema, the description is insufficient. It omits critical context about irreversibility, cascading effects on related entities, and recovery options that would be necessary for safe invocation.

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 'id' parameter is fully documented in the schema), the baseline score is 3. The description adds no additional semantic information about the parameter beyond what the schema provides.

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 course location' is a tautology that restates the tool name (delete_course_location). While it identifies the verb and resource, it fails to distinguish from siblings like delete_meeting_location or other deletion tools.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., update_course_location to disable vs delete), nor does it mention prerequisites such as checking for existing courses at this location.

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