search_tax_rates

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. It does not state that this is a read-only operation, how results are ordered or paginated, what fields are returned, or what happens with no filters supplied. Only the word "search" weakly implies non-mutation.

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?

A single front-loaded sentence with no redundant or filler wording; the core operation is stated first. Its brevity is efficient, though it borders on under-specification rather than tightness.

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?

Even for a simple search tool, a bare one-liner is insufficient when there are no annotations and no output schema to explain return shape or pagination behavior. Nothing tells the agent how to distinguish this from get_tax_rate or what a caller should expect back.

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 reported as 0% at the parameter level, and the description does not compensate: it never names the available filters (name, active) or explains limit semantics such as defaults or maximums. The nested property descriptions inside the schema do the heavy lifting, so the description adds essentially no meaning beyond the structured field.

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?

"Search for tax rates in QuickBooks Online" states a specific verb and resource, so the agent knows exactly what entity is being queried. However, it does not distinguish this tool from siblings such as get_tax_rate (single fetch) or search_tax_codes, and "optional filters" is too vague to convey scope.

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?

There is no guidance on when to use this instead of get_tax_rate, nor on prerequisites, exclusions, or how filtered vs. unfiltered searches behave. The phrase "with optional filters" hints that all filters may be omitted, but the agent must infer that from the schema rather than the description.

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