lookup_bank_account

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

No annotations provided, so description must carry full burden. It mentions the lookup operation but does not disclose behavioral traits such as side effects (likely none), error handling, or response format. Minimal transparency.

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?

A single, concise sentence with no filler words. It efficiently conveys the tool's purpose, though it could be slightly more structured (e.g., clarifying input and output).

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?

Given the tool has 2 simple string parameters and no output schema or annotations, the description is too minimal. It lacks return format, error conditions, and usage context, making it incomplete for reliable agent 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 description coverage is 0%; parameters have no descriptions in the schema. The description mentions 'account number' and 'bank code' but adds no further meaning beyond the parameter names. It does not specify accepted formats, lengths, or examples.

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?

The description clearly states the tool resolves an account name from account number and bank code, using specific verb 'Resolve' and resource 'account name', distinguishing it from sibling tools that create, delete, or list entities.

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?

No guidance on when to use this tool versus alternatives (e.g., get_virtual_account, list_banks). The description only states the function without contextualizing its place among sibling tools.

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