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

Goes well beyond the readOnly/openWorld annotations: discloses the upstream data source and license, that results carry a crosswalk version, that failures return a reason rather than a guess, that IPs are refused and not echoed back, and that calls are free but rate-limited per IP. That is exactly the operational context annotations cannot carry.

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?

Front-loads the core mapping and the accepted inputs before the exclusion list, with no filler sentences. Slightly dense and includes publisher/license provenance that an agent rarely needs, but it is still a compact two-sentence block.

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?

No output schema exists, so the description enumerates the return payload itself: canonical URN, governing-layer stack, OCD-ID, Wikidata QID, precision, failure reason, and crosswalk version. Combined with the refusal semantics, nothing an agent needs to call this correctly is missing.

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 baseline is 3. The description adds real meaning beyond the schema by explaining the two-argument edge pattern (country 'US' plus region 'CA') and the three accepted code forms, clarifying how the two parameters interact rather than just restating them.

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 (maps) and resource (ISO 3166 code → UnGovr jurisdiction), and explicitly scopes itself against the similar-sounding resolve_domain_jurisdiction by listing what it will not resolve (IP addresses, cities, postal codes). An agent can pick between this and list_countries without opening either schema.

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?

Gives clear usage context: accept-country, subdivision, or country+region pairs, and explicit exclusions (IPs refused, city/postal unsupported, XX/T1 return a reason). It stops short of naming sibling tools as alternatives, so the routing guidance is present but not fully explicit.

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