travel_advisories

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

Annotations already declare readOnlyHint=true, covering safety. The description adds context that it returns advisory text, date published, and country information, and that no parameters return all countries. However, it does not disclose potential behaviors like pagination, rate limits, or output format, which are not covered by annotations.

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 three concise sentences, front-loaded with the core purpose. Every sentence adds information: what it does, the level meanings, and the return content. No wasted words.

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 helps by listing the return elements (advisory text, date published, country information) and explaining the filter semantics. It lacks details on potential pagination or error conditions, but for a simple, read-only lookup tool this is adequate and fairly complete.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the meaning of advisory levels (1–4) and clarifying that country_code is a filter for a specific country, plus the no-parameter behavior returns all countries. This goes slightly beyond the schema's brief field descriptions.

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 'Get' and explicitly names the resource: U.S. State Department travel advisories. It clearly distinguishes from any sibling tool by citing the specific government source and scope ('all countries or a specific country').

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 implies when to use the tool (when you need U.S. State Department travel advisories) and clearly states the optional filters. It does not explicitly name alternatives or exclusions, but given the unique nature of the tool, the context is clear enough.

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