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. It implies a read operation but fails to disclose pagination behavior (despite cursor/per_page params), default page sizes, or whether results are cached. The term 'all' is misleading since the endpoint appears paginated.

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 brief (4 words), this represents under-specification rather than efficient conciseness. The single sentence fails to front-load critical information about pagination or filtering capabilities that would help an agent invoke the tool correctly.

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 tool with 7 filter parameters including complex enums (for_type with 6 values) and pagination, the description is inadequate. It mentions none of the filtering capabilities (visibility, use_as_duplicate_indicator) or the relationship between the for_* parameters.

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 (every parameter has a basic description), establishing a baseline of 3. The description itself adds no semantic context about the filtering logic (e.g., how for_user vs for_account interact) or enum meanings beyond what the schema provides.

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 signup_question records' restates the tool name with minimal elaboration. While it identifies the resource (signup_question) and action (get), it fails to distinguish from the many sibling 'get_' tools or explain what distinguishes a 'signup_question' from other record types.

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, when pagination is required, or how to use the filtering parameters (for_user, for_account, for_type) effectively. The agent has no signals about prerequisites or search strategies.

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