eduframe-mcp

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

Annotations cover the safety profile (read-only, non-destructive, idempotent), but the description adds no behavioral context about pagination mechanics, default page sizes, or what constitutes a 'category record' in this domain. It misses the opportunity to clarify that 'all' means 'list endpoint with pagination' rather than a complete dump.

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 the single sentence wastes no words and is front-loaded with the verb, it is arguably too concise for a tool with four parameters including pagination and filtering. It meets brevity standards but fails the 'appropriately sized' criterion for this complexity level.

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 rich input schema (100% coverage) and complete annotations, the description provides minimum viable context by identifying the resource type. However, gaps remain regarding pagination behavior and differentiation from singular-fetch siblings, leaving agents to infer these from schema inspection 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?

With 100% schema description coverage, the schema fully documents all four parameters (cursor, per_page, published, sort). The description adds no parameter-specific guidance, meeting the baseline expectation for well-schematized tools.

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 basic verb and resource ('Get all category records'), and the word 'all' distinguishes it from sibling 'get_category' (singular). However, it fails to indicate that results are paginated (not truly 'all' at once) or that filtering/sorting capabilities exist, which could mislead about the tool's scope.

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 versus 'get_category' for fetching single records, or when pagination parameters are required. No mention of alternative tools or prerequisites for effective usage.

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