eduframe-mcp

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

Annotations declare idempotentHint=true and destructiveHint=false, covering the safety profile. However, the description adds no behavioral context beyond these annotations—omitting whether partial updates are supported, what happens if the ID doesn't exist, or any side effects on child categories via parent_id.

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?

At three words, the description is under-specified rather than appropriately concise. It front-loads no useful information beyond the tool name itself, failing to earn its place as helpful documentation.

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 mutation tool with no output schema, the description inadequately explains the operation's scope. Despite having well-documented parameters, it fails to clarify whether updates are partial (PATCH-like) or full replacement, and omits hierarchical implications of the parent_id field.

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 schema itself documents all 6 parameters (id, name, slug, description, is_published, parent_id) adequately. The description mentions no parameters, meeting the baseline expectation when schema coverage is comprehensive.

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 'Update a category' is a tautology that restates the tool name (update_category). While it contains a verb and resource, it fails to specify what 'category' means in this domain or distinguish from sibling tools like create_category or get_category.

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 tool versus alternatives (e.g., create_category for new categories), nor any mention of prerequisites like requiring an existing category ID. The description offers zero contextual hints for selection.

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