invoiceflow-mcp

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

No annotations provided, so description carries full disclosure burden. Adds valuable pagination behavior ('Supports pagination') beyond structured data. However, lacks safety profile (read-only status), rate limits, default behavior when no filters applied, or return value structure. 'List' implies read-only but explicit confirmation would help.

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 sentence front-loads core functionality and all filter dimensions; second adds pagination capability. Every word earns its place with no filler or redundancy.

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?

With 9 parameters, 0% schema coverage, complex validation patterns (UUID, date-time regex), and no output schema, the description covers the primary use cases but leaves significant gaps. No explanation of return format, error conditions, or the relationship between overdue_only filter and status=overdue.

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 description to compensate. Maps semantic meaning to most parameters by listing filterable concepts (status, client, amount range, date range, overdue status) and mentioning pagination. However, fails to explain data formats (UUID for client_id, ISO8601 for dates), enum values, or default values (limit=20, offset=0).

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?

States specific action (List and filter) and resource (invoices) with clear filtering capabilities (status, client, amount range, date range, overdue status). Effectively distinguishes from sibling mutation tools (invoice_create, invoice_mark_paid) through its list/filter verb, though could explicitly clarify it's for retrieval rather than modification.

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?

Provides no guidance on when to use this tool versus alternatives like cashflow_report (which might aggregate invoice data) or invoice_risk. No mention of prerequisites (e.g., needing client_id from client_manage) or when filtering is preferable to unfiltered listing.

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