eduframe-mcp

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

While annotations correctly declare readOnlyHint=true and destructiveHint=false, the description adds no behavioral context beyond this—omitting details about pagination behavior, default page sizes, or what constitutes a 'custom object' in this domain.

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?

At three words, it is appropriately brief, but suffers from under-specification rather than meaningful conciseness. No structural issues, yet no value per sentence.

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 a sibling specific-getter tool and pagination parameters, the description is incomplete. It should clarify the 'get all' versus 'get one' distinction and acknowledge pagination behavior.

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 (cursor and per_page are fully documented), the baseline score applies. The description provides no additional parameter semantics, but the schema carries the load.

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 custom objects' is a tautology that restates the tool name. It fails to distinguish from the sibling tool get_custom_object_by_object_slug (which retrieves a specific object by slug) or clarify the scope of 'all'.

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_custom_object_by_object_slug for fetching specific objects, nor does it mention pagination requirements despite having cursor/per_page parameters.

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