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 provides minimal information. It does not explain pagination behavior (despite having pagination parameters), rate limits, authorization requirements, or whether 'all' refers to all programs in the system or just those accessible to the authenticated user.

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 brief (3 words), this is under-specification rather than effective conciseness. The single sentence fails to earn its place by not conveying essential context like pagination behavior or differentiation from singular retrieval tools.

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 presence of pagination parameters and numerous sibling tools (including 'get_program', 'create_program', etc.), the description is incomplete. It lacks explanation of pagination, scope of 'all', and differentiation from related tools, leaving agents to infer usage from parameter names alone.

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 input schema has 100% description coverage for both parameters (cursor and per_page), so the baseline score applies. The description adds no additional semantic information about the parameters, but the schema adequately documents them.

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 programs' is essentially a tautology of the tool name 'get_programs'. While it confirms the action (Get) and resource (programs), it fails to distinguish from the sibling tool 'get_program' (singular) or clarify whether this returns a complete unfiltered list versus a scoped 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?

There is no guidance on when to use this tool versus 'get_program' (singular) or other related tools like 'get_program_edition'. No mention of pagination strategy 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.