eduframe-mcp

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

Annotations already declare read-only, idempotent, and non-destructive properties. The description adds no behavioral context about pagination mechanics, filtering behavior, or return structure. It does not clarify that results are paginated despite claiming 'all' records.

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 four words. Front-loaded with verb 'Get'. While efficient, the brevity sacrifices necessary context 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?

Inadequate for a paginated list tool with filtering options. Missing clarification on pagination workflow, email filtering behavior, and differentiation from singular retrieval tools. No output schema exists to compensate.

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 has 100% description coverage for all three parameters (cursor, per_page, email). The description mentions none of them, but meets the baseline score since the schema fully documents the semantics.

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 action (get) and resource (lead records) but fails to distinguish from sibling 'get_lead' (singular). The word 'all' is slightly misleading given the pagination parameters (cursor, per_page) suggest batch retrieval rather than a single complete dump.

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 the singular 'get_lead', or when to apply the email filter versus retrieving unfiltered lists. No mention of pagination workflow.

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