search_payment_methods

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

No annotations exist, so the description carries the full burden. It does not state that this is a non-mutating read, whether results are paginated, what the default limit is, or what the response shape looks like. 'Search' weakly implies read-only, but nothing about authentication, result ordering, or empty-result behavior is disclosed.

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 efficient sentence with no filler, and the resource and scope are front-loaded. It is concise to a fault — nothing is wasted, but the brevity comes at the cost of the missing guidance noted above.

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 a nested parameter object, no annotations, and no output schema, the description is thin: no return-value hints, no pagination or limit behavior, and no filter semantics. An agent could invoke it, but not confidently choose it over get_payment_method or predict what comes 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 at 0% and the parameters are nested inside a required 'params' object, so the description must compensate. Instead it says only 'optional filters' and never names the available filters (name, type, active, limit) or explains how they combine, leaving the agent to open the schema to learn anything actionable.

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?

States a specific verb and resource ('Search for payment methods') plus the system context (QuickBooks Online), which is clear enough to distinguish it from write-oriented siblings like create_payment_method and update_payment_method. It does not, however, contrast itself with get_payment_method, which is the nearest alternative for single-record retrieval.

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?

The phrase 'with optional filters' implies the tool can be called with no filters to list everything, but the description never says when to use this search versus get_payment_method, or what happens when zero filters are supplied. No exclusions, prerequisites, or alternative routing are given.

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