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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact (results are full records including SyncToken, so no follow-up get is required), but omits pagination/truncation behavior, which the schema description carries instead.

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 tight sentences, front-loaded with what the tool returns and then the practical consequence (no separate get, batch by Id). No filler.

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?

There is no output schema, and the description partially compensates by saying results are full records with SyncToken. Combined with the fully documented criteria parameter, an agent has enough to call it correctly, though return shape and paging are only partly addressed.

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 100%, so criteria syntax and operators are already fully documented by the schema. The mention of "Id IN" only echoes what the schema already states about the IN operator, so the baseline 3 applies.

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 (Search) and resource (vendor credit records) scoped to QuickBooks Online, and implicitly separates itself from get_vendor_credit by noting that full records with SyncToken come back so no follow-up get is needed. It never names the sibling tool directly, which keeps it just short of a 5.

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?

Gives one concrete usage pattern ("read several known Ids in one search with Id IN") but does not say when to prefer this over search_vendors/get_vendor_credit or when it is the wrong choice. The batch-read hint is useful context, but the when-not guidance is absent.

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