eduframe-mcp

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

With no annotations provided, the description fails to disclose that results are paginated (despite cursor/per_page parameters), whether the operation is read-only, rate limits, or whether 'all' respects the filter parameters. It omits critical behavioral context that annotations would typically cover.

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 brief (4 words) and front-loaded, but undersized for the tool's complexity. While not verbose, it sacrifices necessary information about pagination and filtering capabilities.

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 with 6 parameters supporting pagination, filtering, and sorting—and no output schema or annotations—the description is inadequate. It fails to mention pagination behavior, filtering capabilities, or the relationship to the singular 'get_user' endpoint.

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%, so parameters are fully documented in the schema itself. The description adds no additional semantic context about parameters (e.g., that cursor/per_page enable pagination, or that label_id accepts multiple values), meriting the baseline score.

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 states the basic function (retrieving user records) using the generic verb 'get', but fails to specify that this returns a paginated list versus the sibling 'get_user' which likely returns a single user. The word 'all' implies unfiltered retrieval, which contradicts the available filter parameters (role, email, label_id).

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 versus the singular 'get_user', or when to apply specific filters. No mention of pagination requirements for large datasets or authentication prerequisites.

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