search_by_country

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by stating 'Paginated' and specifying the return format ('entity list with LEI, legal name, and status for each'). 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?

The description is compact (5 sentences) with a front-loaded purpose, clear USE WHEN and FAILS WHEN sections, and no redundant information.

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 output schema, the description adequately describes the return format (entity list with LEI, legal name, status) and mentions pagination. It covers failure conditions and usage patterns, making it complete for a list tool.

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 coverage is 100% with descriptions for both parameters. The description reinforces the country parameter with examples ('US, GB, DE') and a failure condition, and mentions pagination (implicitly covering limit). Adds nuance 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?

The description uses a specific verb ('List') and resource ('entities registered in a specific country'), immediately clarifying the tool's function. It distinguishes from siblings like 'search_by_bic' and 'search_by_isin' by focusing on country-based filtering.

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?

The description provides explicit example queries ('companies in Germany', 'LEIs from US', 'entities in country X') and a clear failure condition ('FAILS WHEN: country code is not a 2-letter ISO 3166-1 alpha-2 code'), guiding the agent on correct use.

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