Retrieve vendor expense totals for any date range, broken down by vendor. Identify spending patterns and manage payables with clear per-vendor summaries.
Get a Vendor Expenses report for a given date range. Shows expense totals broken down by vendor.
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | End date (YYYY-MM-DD) | |
| start_date | Yes | Start date (YYYY-MM-DD) |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description only states basic retrieval. Doesn't disclose side effects, authentication needs, rate limits, or pagination behavior. Minimal transparency beyond purpose.
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, no fluff. Front-loaded with verb and resource. Efficiently conveys purpose and key detail (breakdown by vendor).
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?
Adequate for a simple report tool: specifies date range and vendor breakdown. However, lacks output format or any additional constraints. No output schema to compensate.
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 clear parameter descriptions. Description adds no new meaning beyond 'date range', which is already in schema. Baseline 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?
Description clearly states the tool retrieves a Vendor Expenses report for a date range, with totals by vendor. This distinguishes it from other QBO reports like profit_and_loss or balance_sheet.
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 guidance on when to use this vs other reports (e.g., aged_payables, customer_sales). No 'when not to use' or alternatives provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.