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

With no annotations, the description carries the full burden and does notable work: it discloses that only 'active, verified' listings are returned, that target_industries/target_business_profiles only re-rank and never exclude eligible listings, and that application_url is a tracked link that must be passed through verbatim with its query string. It omits pagination, result caps, and any auth/rate-limit behavior, so it falls short of full coverage.

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?

Four sentences, front-loaded with purpose, then return semantics, then soft-rank caveat, then the link-handling instruction. Nothing is padded, though the soft-rank point is made twice (in the description and again in the two param descriptions), a mild redundancy.

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 17-param query tool with no output schema and no annotations, the description covers the essentials an agent needs: what it searches, that results are active/verified, that target_* params are ranking-only, and how to handle the tracked URL. Missing pagination/result-count behavior is the main gap, but the parameter schema is exhaustive.

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% across 17 params, including the enum meanings and the apy_min/apy_max distinction, so the schema already does the heavy lifting. The description restates the soft-rank semantics of the two target_* params but adds no format or syntax detail beyond what the schema provides. 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 and resource: 'Query the Bancadia registry for business checking account products using compound filter criteria.' It is unambiguous about what the tool returns (active, verified listings), but it never names or contrasts with the sibling get_business_checking_listing, so the agent must infer that this is the search/browse tool and the sibling is the single-record fetch.

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?

Usage is implied by the filter-oriented phrasing and the explicit soft-rank behavior, but there is no statement of when to prefer this over get_business_checking_listing or when not to use it. The soft-rank explanation does usefully tell the agent not to expect hard exclusion from those two params, which is a form of guidance, but routing between siblings is left to inference.

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