Retrieve a customer balance report for a specific date to list outstanding balances owed by each customer, helping you identify unpaid invoices and track receivables.
Get a Customer Balance report as of a given date. Lists the outstanding balance owed by each customer.
| Name | Required | Description | Default |
|---|---|---|---|
| report_date | No | Report as-of date (YYYY-MM-DD, default: today) |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description indicates a read operation (report) with date parameter, but does not disclose additional behavioral traits such as pagination, data freshness, or whether it modifies data. Basic transparency, but no contradictions.
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?
One sentence, directly stating the purpose and what the report contains. No unnecessary words or information.
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 no output schema, the description provides a high-level idea of the report output ('outstanding balance owed by each customer'), but lacks details like fields or format. Still adequate for a simple report tool.
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 coverage is 100% with one parameter. The description confirms 'as of a given date' aligning with the schema, but adds no further semantics beyond what the schema provides. Baseline score of 3.
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 clearly states the tool gets a Customer Balance report as of a given date, listing outstanding balances per customer. It uses specific verb 'Get' and resource 'Customer Balance report', distinguishing it from other report siblings like qbo_reports_customer_sales.
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 usage guidelines or differentiation from alternative report tools. The description implies use for a date-specific balance snapshot, but does not mention when to choose this over other reports like aged receivables.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.