eduframe-mcp

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

With no annotations provided, the description fails to disclose behavioral traits. It misleadingly claims to get 'all' elements while the schema reveals paginated behavior via cursor/per_page. It omits whether results are sorted, the default page size behavior, or what data structure is returned.

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 three-word description is brief but constitutes under-specification rather than efficient conciseness. No information is front-loaded; the sentence merely restates the tool name without earning its place through substantive guidance.

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?

Lacking annotations, output schema, and any description of return values or error conditions, the tool definition is incomplete. For a paginated list operation with 3 parameters and numerous siblings, the description should explain the pagination model and result set scope.

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 (cursor, per_page, and edition_id are all documented), establishing a baseline of 3. The description adds no additional semantic context regarding parameter interactions or data types beyond the schema.

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 elements' is essentially a tautology of the tool name 'get_program_elements', merely dropping the word 'program'. It fails to specify what constitutes an 'element' in this domain or distinguish from siblings like get_program_element (singular) 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 is provided on when to use this tool versus the sibling get_elements_of_program_edition or when to apply the edition_id filter. There is no mention of pagination workflows 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.