eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to explain side effects (e.g., whether this updates invoice status, allows partial payments, or handles overpayments), idempotency, required permissions, or what the tool returns. For a mutation operation, this lack of behavioral context is a critical gap.

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 extremely brief (3 words), this represents under-specification rather than efficient conciseness. Every word is obvious from the tool name, wasting the opportunity to provide value. The description is front-loaded with no structure, but the content is too minimal to be useful.

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 5-parameter mutation tool with no output schema and no annotations, the description is woefully incomplete. It should explain the payment-invoice relationship, validation rules (e.g., currency matching invoice), and business logic effects, but provides none of this context.

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, establishing a baseline of 3. The tool description adds no parameter-specific context (e.g., date format expectations, whether payment_method_id refers to an existing entity), but also doesn't contradict the schema. Note: The schema itself contains an error where invoice_id is described as 'ID of the payment' rather than 'ID of the invoice', which the description fails to clarify or correct.

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 'Create a payment.' is a tautology that restates the tool's action without clarifying the domain context. It omits that this specifically creates an invoice payment (not a generic payment) and fails to distinguish what kind of payment record is being created despite the tool name implying invoice-specific functionality.

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, prerequisites (e.g., invoice existence/status requirements), or workflow context. Sibling tools like delete_invoice_payment_by_id_and_invoice_id and get_invoice_payments_by_invoice_id suggest a CRUD pattern, but the description doesn't explain the relationship between these operations.

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