eduframe-mcp

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

While annotations declare the operation as destructive and idempotent, the description adds no behavioral context beyond the verb 'Delete'. It fails to disclose what happens to materials contained within the group (cascade delete vs. orphan), whether the deletion is permanent, or any side effects.

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 concise with no redundant words or filler. However, it borders on under-specification—it could add crucial context (like cascade behavior) with only a few additional words without sacrificing clarity.

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 single-parameter destructive operation, the definition is minimally adequate given the rich schema and annotations. However, it lacks domain context regarding sibling tools and the implications of deletion, which are important for an AI agent to avoid destructive errors.

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 for the 'id' parameter, the baseline is met. However, the description contributes no additional semantic information about the parameter (e.g., where to obtain the ID, format constraints beyond the schema) or how it identifies the specific group.

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 uses a clear verb ('Delete') and identifies the resource ('material group'), making the basic purpose unambiguous. However, it does not differentiate from sibling tools like 'delete_material' or explain what constitutes a 'material group' 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'delete_material' or 'update_material_group' to empty a group), nor does it mention prerequisites such as permissions or whether the group must be empty before deletion.

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