eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention pagination behavior, rate limits, authentication requirements, or whether 'all' refers to system-wide tasks or user-scoped tasks. The description implies a complete dump but the schema reveals paginated access.

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 at only four words. While not verbose, it is front-loaded and efficient. However, given the lack of annotations and the presence of pagination features, the description is arguably too minimal to be fully effective.

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 low-complexity list endpoint with 100% schema coverage and no output schema, the description meets minimum viability but has clear gaps. It should clarify pagination behavior and distinguish from 'get_task' to be complete.

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?

Schema description coverage is 100%, with both 'cursor' and 'per_page' fully documented in the input schema. The description adds no additional parameter context (e.g., default pagination behavior), warranting the baseline score for high-coverage schemas.

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 a basic verb-resource action ('Get all task records'), but the term 'all' is misleading given the pagination parameters (cursor, per_page) exist. It also fails to distinguish from sibling tool 'get_task' (singular), leaving ambiguity about when to use the list vs. single-resource endpoint.

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 like 'get_task' or 'create_task'. Does not mention that pagination is required to retrieve the full dataset implied by 'all', or that results are paginated by default.

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