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

No annotations provided, but description adds context about potential large response when no search filter, and explains the relationship with country_banking_rules. Could be improved by mentioning data freshness or rate limits.

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?

Concise and well-structured with an overview, Args section, and examples. No superfluous 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?

Given no annotations and presence of output schema, the description covers purpose, usage, parameters, and a caveat. It references a relevant sibling tool (country_banking_rules). Minor missing aspects like error handling or exhaustive list of code types.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: ISO alpha-2 format, code_type from payment_requirements, optional search filter. Examples illustrate usage.

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 verb 'look up' and resource 'country-specific payment codes (KNP, purpose codes, etc.)'. It distinguishes from siblings by referencing country_banking_rules as a prerequisite.

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 instructs to 'Use country_banking_rules first to see which code types a country requires... then use this tool'. Provides clear examples and explains optional search parameter.

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