Search QuickBooks Online tax codes by name with partial matching to find tax codes needed for invoices, expenses, and reports.
Search TaxCode records by Name (LIKE match).
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Search term matched against Name with LIKE '%term%' | |
| maxResults | No | Maximum number of results to return (default: 100, max: 1000) | |
| startPosition | No | Starting position for pagination (1-based, default: 1) |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only mentions LIKE matching but does not disclose that the operation is read-only, supports pagination, or any other behavioral traits. It fails to compensate for missing annotations.
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?
Description is a single sentence, concise but lacks structure. It front-loads purpose but omits additional useful details. Could be expanded slightly without losing conciseness.
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 tool has pagination params and no output schema, the description should mention that it returns a list, note pagination behavior, or defaults. It is incomplete for a search 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 descriptions for all parameters. The description adds no new information beyond the schema; it merely restates the LIKE matching for 'term'.
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 verb 'Search', resource 'TaxCode records', and method 'LIKE match'. This distinguishes it from sibling tools like get (single record) and list (all records).
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 tool versus alternatives (e.g., list or get). The description lacks context on when LIKE search is appropriate or when to use pagination.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.