invoiceflow-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It effectively describes output content (the eight metrics returned) but fails to declare operational characteristics like read-only safety, idempotency, or whether the projection uses cached vs. real-time data.

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?

Single dense sentence is front-loaded with the core action ('Generate a cash flow summary') followed by colon-separated list of specific output components. Zero wasted words; every clause describes distinct report functionality.

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?

Given the absence of an output schema, the description compensates effectively by detailing specific report components (totals, rates, projections, breakdowns). Minor gap: does not explicitly state the read-only/safe nature of the operation given lack of readOnlyHint annotation.

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?

Input schema contains zero parameters, establishing baseline score of 4 per rubric. No parameter semantics are required or provided.

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 verb 'Generate' and resource 'cash flow summary', then enumerates eight distinct metrics (collection rate, 30-day projection, breakdown by status/client) that clearly distinguish this analytical/reporting function from transactional sibling tools like invoice_create or invoice_mark_paid.

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 detailed list of aggregated metrics implies this tool is for financial analysis rather than individual record management, there is no explicit guidance on when to prefer this over invoice_list for detailed records or how it relates to payment_reconcile for collection data.

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