worldpop

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 and it says almost nothing: no indication of whether this is a live upstream fetch or a static catalog, no pagination or result-size guidance, no rate-limit or availability notes. Only the read-only nature is inferable from the word 'metadata'. The presence of an output schema covers return values, which keeps this above 1.

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?

Two short sentences, with the resource stated first and the filter behavior second — nothing extraneous. It is efficient, though its brevity edges toward under-specification rather than tightness.

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?

For a one-parameter read tool with an output schema, the description is minimally viable: the agent knows the source and the filter. It still leaves out what the metadata contains (resolution, vintage, version), whether results are paged, and how this differs from other dataset-listing siblings.

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% — the single parameter carries only a title 'Iso3' and a default of ''. The description does add value by clarifying this is an ISO3 country code used as a filter, but it omits the expected format (three-letter ISO 3166-1 alpha-3, case sensitivity) and whether the empty default returns all datasets.

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 names the resource ('WorldPop population grid datasets metadata'), so an agent knows roughly what it returns, but there is no verb and it is ambiguous whether this lists dataset catalog entries or returns population figures. It also does nothing to distinguish itself from adjacent catalog-style siblings such as hdx_datasets, data_sources, or ms_global_buildings.

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?

'Filter by ISO3 country' hints that the parameter is an optional narrowing filter, but there is no statement of when to reach for this tool versus the many other population/displacement/dataset siblings. No exclusions, no prerequisites, no indication of what happens with an empty filter.

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