eduframe-mcp

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

The description adds no behavioral context beyond what the annotations already provide (idempotentHint: true, destructiveHint: false). It does not clarify whether adding a label replaces existing labels or appends to them, what validation occurs, or what constitutes a successful operation.

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 at four words with no redundant or wasted language. However, it is under-specified rather than efficiently informative—appropriate length for the content provided, but lacking necessary detail.

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 parameter ambiguity (two ID fields with confusing descriptions) and lack of output schema, the description should clarify parameter usage and expected outcomes. It leaves critical gaps regarding which identifier corresponds to which resource and what the tool returns upon success.

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 applies. However, the schema descriptions are confusingly similar (both referencing 'label'), and the description fails to disambiguate that 'id' likely refers to the order while 'label_id' refers to the label. It neither clarifies the relationship nor adds semantic meaning beyond the schema's flawed descriptions.

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 'Add label to an order' is a tautology that merely restates the tool name in sentence case. While it identifies the verb (add) and resources (label, order), it fails to distinguish this tool from siblings like create_label (which creates the label entity itself) or clarify the nature of the association being created.

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, prerequisites (e.g., whether the label and order must already exist), or expected workflow sequences. There is no mention of related operations like removing labels or updating orders.

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