Get Visa Info

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

Annotations declare readOnlyHint=true, and description matches a read operation. Adds behavioral context that it returns visa/ESTA/eTA requirements. 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?

Two sentences, no fluff, information front-loaded. Each sentence serves a clear purpose: what the tool returns and how to use parameters.

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?

Simple tool with 2 parameters, no output schema, read-only. Description sufficiently explains input options and output intent, leaving no ambiguity for an AI agent.

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 both parameters with descriptions; description adds value by explaining acceptable formats for 'team' (ID, FIFA code, country name) and case-insensitivity, and clarifies 'host_country' is optional filter.

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?

Specifies verb 'Returns', resource 'visa/ESTA/eTA requirements', and scope ('for any team's nationals entering the three host countries'). Distinct from sibling tools like 'get_matches' or 'get_standings'.

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?

Clear usage context: for World Cup travelers needing entry requirements. Accepts multiple identifier types and optional filtering. Does not explicitly mention when not to use, but sibling tools cover other domains.

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