invoiceflow-mcp

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

With no annotations provided, the description carries the full burden. It successfully discloses key side effects (PDF generation, status update to 'sent', email delivery) but omits critical mutation safety details like idempotency, reversibility, error handling if email fails, or required permissions.

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?

Three short sentences with zero waste. The description is front-loaded with the core action ('Send an invoice to the client via email') followed by implementation details (PDF generation, status update). Every sentence 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 2-parameter tool without output schema, the description adequately covers the core functionality. However, given this is a destructive mutation (status change, external email delivery), it should mention prerequisites or state requirements for the invoice before sending.

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%, so the schema already fully documents both invoice_id and message parameters. The description adds no additional parameter-specific context (e.g., format constraints, default behavior when message is omitted), warranting the baseline score 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?

The description uses specific verbs (send, generates, updates) and clearly identifies the resource (invoice) and scope (via email, status change to 'sent'). It effectively distinguishes from siblings like invoice_create, invoice_list, and invoice_mark_paid by specifying the email delivery and PDF generation aspects.

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?

While the description implies this is for initial invoice delivery, it lacks explicit guidance on when to use this versus invoice_remind (which likely sends reminder emails). No prerequisites are stated, such as required invoice status (e.g., 'draft' vs 'ready') before sending.

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