invoiceflow-mcp

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

With no annotations provided, the description carries full burden but only minimally discloses behavior. It mentions that amount_paid and status fields are updated, but fails to address idempotency, reversibility, validation constraints (e.g., overpayment handling), or side effects like notifications triggered.

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?

Two sentences with zero waste. The first sentence front-loads the primary action and scope; the second explains the specific data mutations. Every word 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 financial mutation tool with no annotations and no output schema, the description is insufficient. It omits critical context such as whether the operation is reversible, what status values result (paid vs partial), and what the tool returns upon success or failure.

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 a baseline of 3. The description adds slight value by explaining the 'fully or partially paid' concept which maps to the amount parameter's default behavior, but does not elaborate on syntax, format, or relationships between parameters beyond what the schema provides.

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 clearly states the core action (mark as paid) and scope (fully or partially), and distinguishes from siblings like invoice_send or invoice_create by mentioning specific fields updated (amount_paid and status). However, it does not explicitly differentiate from payment_reconcile.

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 on when to use this tool versus alternatives (particularly payment_reconcile), no prerequisites mentioned (e.g., invoice must exist), and no warnings about irreversible actions or validation rules.

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