eduframe-mcp

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

The annotations already establish this is a write operation (readOnlyHint: false) and non-idempotent (idempotentHint: false). The description adds no behavioral context beyond these annotations— it doesn't explain that multiple calls create duplicate invoices, doesn't describe the invoice lifecycle (draft vs. final), and doesn't clarify the nested invoice_items structure.

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?

The description is extremely brief (3 words), which prevents verbosity, but it is too minimal to be genuinely useful. The single sentence structure is efficient, yet it wastes the opportunity to provide substantive guidance that an AI agent would need.

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 4 parameters including a complex nested array structure (invoice_items_attributes) and no output schema, the description is inadequate. It fails to mention the account relationship, line item requirements, or the existence of the nested invoice items structure, leaving critical gaps in understanding.

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?

With 75% schema description coverage, the input schema adequately documents most fields (account_id, feature, footnote, and nested item fields). The description adds no additional parameter context, but the baseline score of 3 is appropriate since the schema carries the semantic burden.

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 verb and resource ('Create an invoice'), but fails to distinguish from siblings like create_invoice_payment_by_invoice_id or create_invoice_vat. It provides minimal information beyond the tool name itself, falling into vagueness regarding scope and 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?

There is no guidance on when to use this tool versus alternatives (e.g., when to use create_invoice_payment_by_invoice_id versus creating an invoice first). No prerequisites are mentioned, such as requiring a valid account_id or the relationship to catalog variants for line items.

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