eduframe-mcp

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

The description aligns with annotations (read-only operation) and implies pagination scope with the word 'all', but adds no information about return format, rate limits, or what data the records contain.

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 concise single sentence with verb-fronted structure. While efficient, it borders on under-specification given the domain ambiguity of 'edition description sections'.

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?

Adequate for a simple paginated list endpoint with strong annotations, but lacks explanation of the return data structure or the relationship between description sections and program editions.

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?

With 100% schema description coverage, the schema adequately documents cursor and per_page parameters. The description adds no additional parameter context, meeting the baseline expectation.

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 verb (Get) and resource (edition description section records) clearly, but fails to distinguish from similar sibling tools like get_elements_of_program_edition or explain what constitutes a 'description section' versus other edition-related data.

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 alternatives such as get_program_edition or get_elements_of_program_edition, nor does it mention prerequisites like needing a specific edition ID.

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