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 mention pagination behavior, default sorting, result limits, or whether results are user-scoped or global. The word 'all' is potentially misleading given the pagination parameters.

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 brief at four words. While not verbose, it wastes the opportunity to add value given the tool's complexity (6 parameters, pagination). It is appropriately sized but underweight for the functional complexity.

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 list endpoint with 6 parameters including pagination controls and no output schema, the description is inadequate. It should explain the pagination model (cursor-based), filtering capabilities, and relationship to singular retrieval tools.

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?

Schema description coverage is 100%, with each parameter (cursor, per_page, creator_id, created_at_after, catalog_variant_id, sort) already documented. The description adds no parameter-specific guidance, 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 'Get all order records' is tautological, restating the tool name without adding specificity. It fails to distinguish from sibling tool 'get_order' (singular) or clarify whether this returns a comprehensive list or filtered subset.

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 'get_order' (singular) or other order-related tools like 'approve_order' or 'cancel_order'. The description omits critical context about pagination despite the presence of cursor and per_page parameters.

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