Look Up Bank by BIC/SWIFT

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

Annotations already declare safe/read-only behavior. Description adds specific return fields and clarifies that unknown or malformed BICs return an error, not a fabricated guess. No contradictions.

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?

Front-loaded with purpose, followed by concise details and usage. Every sentence adds value; no filler or 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?

Even without output schema, description enumerates all return fields and explains error behavior. Tool is simple (one param) and description covers everything needed for correct invocation.

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 covers parameter fully (100% coverage). Description reinforces length rules, gives concrete examples (DEUTDEFF, DEUTDEFF500), and distinguishes head office vs branch BICs.

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?

Clearly states verb (look up) and resource (financial institution by BIC), specifies return details (bank name, city, etc.), and immediately distinguishes from sibling IBAN tools.

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?

Explicitly describes when to use: to resolve BIC, confirm SWIFT code, enrich IBAN. Does not exclude alternatives, but context is clear. Sibling tools are unrelated (IBAN-focused), so no confusion.

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