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 but offers minimal information. It states 'all' implying unfiltered retrieval, but lacks details on rate limits, default sorting, maximum page sizes, or whether the operation is idempotent/safe.

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 description is extremely concise at four words, but this brevity results in under-specification rather than efficiency. While not verbose or poorly structured, it wastes the opportunity to provide necessary context in the front-loaded position.

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?

For a list endpoint with standard pagination, the description fails to explain the referral entity structure, relationships to other objects (like users or programs visible in siblings), or the pagination implementation details. Without an output schema, the description should compensate but does not.

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 for both parameters (cursor and per_page), clearly documenting pagination mechanics. The description adds no parameter-specific context, but the schema adequately compensates, 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?

The description 'Get all referral records' is tautological—it merely restates the tool name 'get_referrals' with the addition of 'all' and 'records'. It fails to specify what constitutes a 'referral' in this domain (e.g., student referrals, program referrals) or how this relates to similar concepts like leads visible in the sibling list.

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 alternatives, nor any mention of pagination behavior beyond the parameter names. The description does not indicate whether this retrieves historical referrals, active referrals, or filtered subsets.

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