search_tax_agencies

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It implies a read-only search but never states that, and it says nothing about whether the name filter is exact or substring matching, whether results are paginated by default, what the default limit is, or what the response looks like.

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 filler or redundancy. It is efficient, though its brevity is partly the cause of the gaps scored elsewhere rather than a sign of tight completeness.

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?

For a tool with no annotations and no output schema, the description should at least describe the return shape and pagination behavior. A search tool with a documented `limit` parameter and no statement about ordering, maximum page size, or total counts leaves the agent guessing on how to retrieve all agencies.

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?

The schema's top-level parameter is a nested `params` object with 0% description coverage at that level, and the description only adds the vague phrase "optional filters." It does not explain that `name` is a partial-match filter or how `limit` interacts with result truncation, so it fails to compensate for the coverage gap.

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 names a specific verb and resource ("Search for tax agencies") and scopes it to QuickBooks Online, which lets an agent distinguish it from the sibling get_tax_agency (single-record fetch). It stops short of explicitly contrasting itself with that sibling or with search_tax_codes/search_tax_rates, so differentiation is only inferable from the name.

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?

"With optional filters" implies this is the list/browse entry point and that calling it with no filters is valid, which is useful implied guidance. However, there is no explicit statement of when to prefer this over get_tax_agency when a specific agency is known, and no prerequisites or exclusions are given.

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