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

Discloses that results may include partner data (aligning with openWorldHint), notes conditional availability of bonuses/APY, and explicitly states the tool does not open accounts, directing users to provider website. Adds behavioral boundaries beyond annotations.

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?

Three sentences with clear structure: action, return info, boundary. No filler or redundant text.

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?

Covers filtering parameters, result contents, partner data caveat, and post-search action. With output schema present and simple parameter set, description is sufficiently comprehensive.

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 already describes both parameters fully (industry, monthlyTransactions). Description only restates them as optional criteria, adding no semantic detail beyond schema.

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?

Uses specific verb 'Search' with resource 'business banking accounts', clearly distinguishing from sibling tools like compare_business_loans. Explicitly states it does not open an account, reinforcing its read-only search purpose.

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?

Implicitly indicates usage for comparing business banking accounts by stating matching criteria, but lacks explicit alternatives or exclusions. Satisfies clear context without explicit 'when not to use' guidance.

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