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

Annotations already indicate readOnlyHint=true and openWorldHint=false. The description adds substantial behavioral context: weekly update cadence, methodology (composite z-score of advisory levels and bulletin severity), and output components (score, trend, confidence, auditable source lineage). This goes beyond the annotations alone.

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 two sentences, front-loading the main purpose, then use cases and update frequency. Every clause adds value; no filler.

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?

The description explains the return components (score, trend, confidence, lineage), the index scale (0-100), update frequency, and history to 1973. Given no output schema, this adequately covers what the agent needs to select and invoke the 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?

The schema fully documents the single optional 'days' parameter with range, meaning, and Gold tier restriction. The description does not add parameter-specific information, but baseline 3 applies given 100% schema coverage.

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 clearly states it returns a 0-100 travel-demand and safety-openness index based on State Department advisory levels, with score, trend, confidence, and auditable source lineage. The verb 'Returns' and specific resource make the purpose specific and distinguishable from the opaque sibling IDs.

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 explicitly lists when to call this tool (questions about global travel demand, tourism outlook, travel safety, advisory risk, and hospitality pricing/booking decisions). It lacks explicit when-not or alternative tool references, but provides strong contextual use cases.

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