Country profile

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds useful content about which datasets are merged and that figures are 'latest', but says nothing about rate limits, data recency lag, or coverage caveats. Baseline 3 is appropriate with annotations carrying the safety burden.

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 the scope front-loaded ('One-call humanitarian snapshot of a country') and the returned contents listed after a colon. Every clause earns its place; no filler or repetition of the title.

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?

An output schema exists, so return-value shape need not be explained, and the description adequately frames a read-only aggregate. It stops short of noting staleness of the 'latest' data or the comparative use case versus compare_countries, which would make it fully self-sufficient.

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% with only 2 parameters, and the schema itself documents the ISO3/name acceptance pattern and the locale enum in detail. The description adds no syntax, format or default information beyond what the schema already provides, so the baseline 3 applies.

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 the resource (a country) and enumerates the three payloads returned: hosted displaced population by category, population displaced FROM the country, and top origin countries. This clearly distinguishes it from siblings like search_country, compare_countries and refugee_population, though the verb is implicit ('snapshot') rather than an explicit retrieval verb.

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 phrase 'one-call' implies this consolidates data that siblings such as refugee_population, top_host_countries and demographics expose separately, so a reader can infer when to prefer it. However, there is no explicit when-to-use/when-not-to-use statement nor a named alternative, leaving the routing to inference.

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