eduframe-mcp

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

While annotations correctly flag the operation as destructive and idempotent, the description adds no behavioral context about what happens to existing records referencing this option, whether deletion is permanent, or side effects beyond what the annotations state.

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 single-sentence description is efficiently structured with the action verb front-loaded. However, extreme brevity results in under-specification rather than true conciseness, as every word is necessary but insufficient.

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 with three required parameters and no output schema, the description is inadequate. It fails to explain the hierarchical relationship between object_type, field_slug, and id, or to describe the idempotency behavior implied by the annotation.

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 baseline is 3. The description does not add parameter semantics, but it doesn't need to compensate. Note: The schema confusingly uses identical descriptions ('ID of the parent resource') for both object_type and field_slug, which the description does not clarify.

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 ('option from custom field'), distinguishing it from siblings like 'add_option_to_custom_field' or 'update_option_of_custom_field'. However, it lacks specificity about what 'option' means (e.g., dropdown value) and omits scope details.

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 like 'update_option_of_custom_field', nor does it mention prerequisites (e.g., whether the option must be unused) or consequences of deletion.

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