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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds valuable content beyond that: the advisory is a 1-4 level with a summary plus Veabird's local safety notes, telling the agent what the payload contains. It stops short of disclosing freshness or caching behavior.

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 with no filler, front-loading the primary return value (advisory level and summary) before the supplementary local notes. Nothing is wasted.

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 no output schema, the description carries the return-value burden and does so by naming the level, summary, and safety notes. For a two-parameter read tool this is largely complete; the only small gap is not stating what happens if both or neither optional parameter is supplied.

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 50% (only 'country' is documented as an ISO2 code). The description compensates by clarifying the 'resort' parameter's role: it resolves to the resort's country, so the agent understands the two parameters are alternative input paths to the same underlying lookup. This adds meaning beyond the bare 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 names a specific resource (US State Department travel advisory) and scope (crime and safety, level 1-4 plus summary and local notes), so the agent knows exactly what it returns. It does not explicitly contrast with adjacent siblings like hurricane_threats or sargassum_forecast, but the 'crime and safety' framing makes the domain distinction clear enough.

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?

Usage is only implied: the agent can infer this is for looking up a country's or resort's safety advisory, and the phrase 'a beach resort's country' hints at the resort path. There is no explicit when-to-use, when-not-to-use, or alternative named, so guidance stays at the implied level.

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