unhcr_refugees

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only source query, the data update cadence, coverage limitations, authentication requirements, or how the year parameter affects results.

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 a single front-loaded phrase with no wasted words. Its brevity is appropriate structurally, even though important semantic and usage details are omitted.

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 output schema covers return values and the parameter list is small, but the description leaves key call-relevant questions unanswered: what year means, whether country filtering is possible, and how this dataset differs from related displacement tools. It is not complete enough to support confident selection versus alternatives.

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 0%, and the description does not mention the single year parameter. It is unclear whether year refers to the data reference year, publication year, or something else, and no valid range or default behavior is explained beyond the schema's default 2024.

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 identifies the exact resource: UNHCR refugee/IDP population figures by country. It is clear enough to know what the tool returns, but it lacks a retrieval verb and does not distinguish this from siblings like displacement or worldpop.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling tools provide related displacement/population data. The agent must infer usage from the title-like fragment alone.

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