invoiceflow-mcp

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

With no annotations provided, the description carries the full burden. It successfully discloses auto-calculation behavior for financial fields and the invoice number generation format (INV-YYYY-NNNN), but omits safety/risk information such as idempotency, error handling, or whether the operation is reversible.

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?

Three sentences with zero waste. Front-loaded with the core purpose ('Create a new invoice...'), followed by behavioral details (calculations, numbering). Every sentence earns its place.

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 7 parameters, nested line item structures, and no output schema or annotations, the description covers the essential creation flow but leaves significant gaps. It does not describe return values, error conditions, or required vs optional fields, forcing reliance on an undescribed schema.

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 description coverage is 0%, requiring the description to compensate. While it implicitly references client_id and line_items, it fails to explain the other five parameters (currency, issue_date, due_date, notes, terms) or the structure of line item objects (description, quantity, unit_price, etc.).

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 uses a specific verb ('Create') with clear resource ('invoice') and scope ('for a client with line items'). It effectively distinguishes from sibling tools like invoice_list, invoice_send, and invoice_mark_paid through the explicit creation intent.

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 siblings (e.g., when to create vs. update), nor any mention of prerequisites such as whether the client_id must exist beforehand or validation rules for line items.

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