invoiceflow-mcp

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

No annotations provided, so description carries full burden. It discloses specific mutation side effects ('Increments reminder count and updates last_reminder_at'), which is valuable. However, it lacks information on idempotency, error conditions (e.g., if already paid), permissions, or return values.

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: first states purpose, second discloses side effects. Front-loaded and appropriately sized for the tool's complexity.

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 simple two-parameter mutation tool without output schema. The description covers the primary behavioral impact (state updates) but does not clarify the return value or success/failure indicators, leaving a minor gap in completeness.

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 100% (both invoice_id and message have descriptions). The description does not add parameter-specific semantics (e.g., format constraints for invoice_id, message length limits) beyond what the schema already provides, meeting the baseline for high-coverage schemas.

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 action ('Send a payment reminder') and target resource ('unpaid invoice'). The mention of 'reminder' distinguishes it from sibling 'invoice_send' (likely for initial delivery), and 'unpaid' distinguishes from 'invoice_mark_paid'. However, it does not explicitly articulate these distinctions.

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 explicit guidance on when to use versus siblings (e.g., when to remind vs. send initial invoice), no prerequisites stated, and no alternative tools mentioned. Usage must be inferred solely from the 'unpaid invoice' qualifier.

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