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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety behavior is covered by structured data. The description adds useful content-level semantics (the meaning of levels 1-4), but says nothing about freshness, caching, or sourcing cadence that an agent might need beyond the safety profile.

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 dense sentence, front-loaded with the resource and immediately followed by return content, query modes, and formats. No filler or repetition.

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?

With an output schema present, annotations covering safety, and 100% parameter coverage, the description only needs to orient the agent — which it does, covering both the single-country and threshold-list modes. Minor gap: it does not warn about level drift/update timing for an openWorld advisory source.

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%, so both parameters are already documented in the schema. The description reinforces this with concrete format examples (MX, GB, JP) and the level scale, but adds only marginal meaning beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific resource (U.S. State Department travel advisories) and states exactly what is returned: a country's level (with the full 1-4 scale named), summary, and main risk factors, or a filtered list of countries. This is distinguishable at a glance from siblings such as get_airport_status or check_trip_delay_risk.

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 makes the two operating modes explicit — look up a single country, or list every country at or above a given level — which tells the agent when each parameter applies. It stops short of naming alternatives or exclusions, so it is clear context rather than full when/when-not guidance.

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