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

Beyond the readOnlyHint=true annotation, the description discloses the data source (US State Department), the scoring methodology (z-scored daily), the update frequency ('Updates: daily'), and the specific output components. This gives the agent a rich understanding of what the tool returns and its freshness, going well beyond the minimal annotation.

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-loaded with the core return value, then immediately lists output components and usage scenarios. Every clause carries informational weight, with no filler or redundancy. The 'Updates: daily' is appended compactly at the end.

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?

Given the tool's moderate complexity (multiple output components and an optional history mode), the description fully enumerates what is returned, the data coverage, and the use cases. The schema handles the parameter details, and the description provides enough context for an agent to select and invoke the tool correctly without an output schema.

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 covers 100% of the parameter descriptions, including the optional 'days' parameter with full semantics about history series and Gold tier requirements. The tool description itself does not add parameter-specific meaning, but per the rubric, the high schema coverage sets a baseline of 3; there is no gap to compensate for.

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 opens with 'Returns a 0-100 world travel-safety risk composite' which is a specific verb and resource, further clarified by 'z-scored daily from US State Department advisories across ~225 countries'. It enumerates the exact outputs (per-risk-type counts, level-4 do-not-travel list, decoded per-country advisory table), making the tool's function unmistakable and distinct from general health or risk tools.

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 states 'Call when the user asks about travel safety, country risk factors, or do-not-travel status, or when timing international trips, employee travel approvals, or itinerary changes.' This provides clear, scenario-based guidance for when to use the tool, effectively differentiating it from sibling tools in the large catalog.

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