eduframe-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to state what happens when the order ID is not found, what fields are returned, or whether authentication is required, beyond the implied read-only nature of the verb 'Get'.

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?

While the four-word sentence is technically concise, it exemplifies under-specification rather than meaningful conciseness, failing to earn its place by providing actionable guidance for tool selection or differentiation from siblings.

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 absence of an output schema and annotations, and the presence of closely named sibling tools like `get_orders`, the description is insufficiently complete as it fails to clarify the tool's specific scope, return value structure, or filtering behavior.

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?

The schema has 100% description coverage for the single `id` parameter ('ID of the order to retrieve'), establishing a baseline score of 3. The description adds no additional semantic context about the parameter, but none is needed given the comprehensive schema documentation.

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 'Get an order record' restates the tool name 'get_order' without adding specificity about what constitutes an order record or how it differs from retrieving multiple orders via the sibling tool `get_orders`.

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 single-record retrieval tool versus the `get_orders` sibling tool, nor does it mention prerequisites such as needing a valid order ID beforehand.

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