eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no behavioral context beyond these annotations—no information on caching, rate limits, or what constitutes a 'record' (fields returned, depth of data).

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?

Extremely brief at four words, which prevents verbosity, but crosses into under-specification. The single sentence states the obvious without earning its place by adding distinctive value.

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?

Despite low complexity and good structured metadata, the description fails to address the critical distinction between singular retrieval (this tool) and list retrieval (get_courses). For a tool with 100% schema coverage and safety annotations, this omission makes it incomplete.

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% (parameter 'id' is documented as 'ID of the course to retrieve'), so the description is not required to compensate. However, the description itself mentions no parameters, earning only the baseline score.

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?

States the basic action (Get) and resource (course record) but is vague regarding scope compared to sibling 'get_courses'. It implies singular retrieval but doesn't clarify whether this fetches by ID or returns the first course found, leaving ambiguity against the plural variant.

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?

Provides no guidance on when to use this tool versus 'get_courses' or other course-related siblings. No mention of prerequisites (e.g., needing a valid course ID) or error conditions (e.g., course not found).

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