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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value beyond them: that returns are full records including SyncToken (eliminating follow-up reads) and that the tool is region-restricted to AU/CA/UK entities.

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 dense sentences with no filler, and the most decision-relevant information (what it searches, region restriction) is front-loaded. Every clause carries information an agent needs.

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?

With no output schema, the description compensates by describing the shape of results (full records with SyncToken) and the region constraint, while pagination and criteria mechanics live in the schema. Adequate for a two-parameter read tool, though the returned record structure itself is only loosely characterized.

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% and the criteria parameter is exhaustively documented in the schema, so the baseline is 3. The description adds a genuinely useful usage idiom for that parameter (querying several known Ids in a single call with Id IN) that the schema only implies via the operator list.

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+resource (search tax payment records), defines scope precisely (sales tax payments/refunds recorded against filed returns), and adds a hard constraint (AU, CA and UK companies only). This clearly separates it from siblings like search_tax_agencies, search_tax_codes, search_tax_rates and get_tax_payment.

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 concrete routing guidance: results are full records with SyncToken so a follow-up get is unnecessary, and multiple known Ids can be read in one call via Id IN. It also states an eligibility condition (AU/CA/UK only). It stops short of explicitly naming get_tax_payment as the alternative for single-record retrieval, but the implication is clear.

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