Latest statistics

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the useful behavioral fact that output scope depends on whether country is supplied, but it omits data freshness/update cadence and says nothing about the return structure or failure modes.

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?

Three short front-loaded fragments with no filler, and the global-vs-country distinction is stated up front. Slight redundancy with the schema's country parameter description keeps it from a 5.

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 values need not be explained. However, for a tool whose selling point is being the 'most recent' figures, the description never states what 'latest' means (reference date, update frequency, dataset vintage), and the role=origin case is silently unaddressed.

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 100%, so the role, locale, and country parameters are already fully documented in the schema, which sets the baseline at 3. The description only partially reinforces this—'latest hosted figures' loosely matches role=asylum and arguably understates role=origin (displaced FROM the country), which the schema covers far better.

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?

States a specific verb+resource ('Most recent displacement figures') and immediately narrows scope by country presence/absence. It does not name or differentiate itself from close siblings such as refugee_population, country_profile, or trend_analysis, so the agent must infer which one to choose.

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?

It gives the two invocation shapes (with country vs. without) but frames them as parameter behavior rather than as when-to-use guidance against alternatives. No exclusions or sibling routing are provided, so usage is only implied.

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