invoiceflow-mcp

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

Discloses upsert behavior (create or update) but with no annotations, fails to explain critical mechanics: how existing clients are identified for updates, idempotency, or side effects. The claim of updating is unsupported by the schema which lacks an ID parameter.

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?

Extremely efficient: two sentences, front-loaded with action, no redundancy. Every word serves a purpose.

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?

Inadequate for complexity: 9 undocumented parameters, upsert behavior, no output schema, and no annotations. Missing essential details like identification logic for updates, return values, or field semantics.

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?

Complete failure: schema has 0% description coverage for 9 parameters, and the description adds zero parameter context. No explanation of what distinguishes required fields (name/email) from optional ones, or semantic details like tax_id format.

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?

Clearly states the dual create/update capability with specific verbs, and distinguishes from sibling invoice tools by noting the prerequisite dependency ('Clients are needed before creating invoices').

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 implicit sequencing guidance (use before creating invoices) but lacks explicit when-to-use vs. alternatives, prerequisites, or how to determine whether to create or update.

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