invoiceflow-mcp

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

No annotations provided, so description carries full burden. Discloses critical mutation ('Auto-marks the invoice as paid') but omits failure modes (what happens if no match found, multiple matches, or amount mismatch), authorization requirements, or idempotency guarantees for financial operations.

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 efficient sentences with zero waste. First sentence establishes matching mechanism and key parameters; second discloses side effects. Information is front-loaded and dense.

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?

Adequate for a 4-parameter reconciliation tool, covering core workflow and side effects. However, lacks output description (what identifier is returned?) and error handling details given the financial domain and absence of output 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 coverage is 75% (payment_method lacks description). Description compensates partially by mentioning 'Stripe or PayPal' as examples for payment_method and clarifies the matching logic combining amount and email. Baseline 3 appropriate given schema does heavy lifting for other parameters.

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?

Clear specific verb ('Match') with resource ('payment' to 'invoice') and exact matching criteria ('by amount and client email'). Distinguishes from sibling invoice_mark_paid by emphasizing the matching workflow rather than direct status update.

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 context through matching logic but lacks explicit guidance on when to use this versus invoice_mark_paid or how to handle cases where automatic matching fails. No mention of prerequisites (e.g., invoice must exist).

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