eduframe-mcp

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

While annotations correctly declare the operation as read-only and idempotent, the description adds no behavioral context beyond these hints. It fails to disclose what happens when the ID is not found (404 vs null), response format, or whether the lead data includes related entities.

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?

At four words, the description is certainly concise, but it approaches tautology (restating the function name 'get_lead' as 'Get one lead record'). While no sentences are wasted, the extreme brevity constitutes underspecification rather than efficient information density.

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 simple single-resource lookup with good annotations and complete schema coverage, the description is minimally adequate. However, given the lack of output schema, it should ideally characterize the returned lead object or mention error handling to be fully 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?

The input schema has 100% description coverage ('ID of the lead to retrieve'), so the description is not required to compensate. The description mentions no parameters, meeting the baseline expectation when the schema fully documents the single required field.

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 action ('Get') and resource ('lead record'), and uses 'one' to implicitly distinguish from the sibling 'get_leads'. However, it lacks domain context about what constitutes a 'lead' and does not explicitly differentiate from other lead-related operations like update_lead or delete_lead beyond the verb used.

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 is provided on when to use this single-record lookup versus the bulk 'get_leads' alternative, nor are prerequisites (like ID availability) or error scenarios (e.g., invalid ID) mentioned. The agent must infer usage solely from the singular parameter schema.

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