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. While 'Get' implies a read-only operation, the description omits pagination behavior (despite cursor/per_page parameters), side effects, rate limits, or whether 'all' implies unbounded retrieval or respects 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 single sentence is brief but constitutes under-specification rather than efficient conciseness. It fails to earn its place by adding no informational value beyond the tool name itself, leaving the agent without actionable context.

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 multiple similar sibling tools and the ambiguous domain terminology ('program personal program elements'), the description is insufficient. Without an output schema or annotations, the description needed to explain the entity type and relationships, but provided none.

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?

Input schema has 100% description coverage for both parameters (cursor and per_page), establishing a baseline score of 3. The description adds no additional parameter context (e.g., default pagination limits, cursor format), but the schema compensates adequately.

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 program personal program elements' is tautological, merely expanding the snake_case tool name into a sentence without clarifying what 'program personal program elements' actually refers to. It fails to distinguish this tool from siblings like 'get_program_elements' or 'get_elements_of_program_edition'.

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 the many sibling tools that appear to retrieve similar entities (e.g., 'get_program_elements', 'get_program_edition_of_elements_batch'). No mention of prerequisites or filtering capabilities.

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