eduframe-mcp

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

Annotations declare read-only/idempotent safety, so description properly focuses on adding the crucial output format detail (base64 encoding) that annotations lack. However, fails to explain why pagination parameters (cursor, per_page) exist for a singular 'PDF' retrieval.

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?

Single efficient sentence with zero waste. Front-loaded with action verb, immediately specifies encoding format (base64) and resource type (PDF) which are critical for correct invocation.

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?

Without output schema, the description adequately specifies the return format (base64). However, the presence of pagination parameters vs singular 'PDF' description creates an unresolved ambiguity that should have been addressed for a complete definition.

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 coverage is 100%, establishing baseline 3. Description doesn't add parameter-specific semantics, but the schema adequately documents the 'id' as referring to a parent resource. The pagination parameters remain semantically confusing given the singular tool purpose.

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?

Specific verb 'Get' + resource 'invoice PDF' + format 'base64 encoded' clearly defines the scope. Distinguishes from sibling 'get_invoice' (which returns invoice metadata) by specifying PDF file content retrieval.

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?

Implies usage (when you need the actual file content vs metadata), but lacks explicit when-to-use guidance comparing it to 'get_invoice' and doesn't mention prerequisite steps like obtaining the invoice ID.

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