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

There are no annotations, so the description must carry the behavioral burden. It describes the data content but does not disclose operation characteristics such as whether this is a read-only listing, whether the list is static or dynamic, or what the exact response format is.

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 short and front-loaded with the essential content: what is listed and what each entry contains. The final sentence is slightly stylistic but still conveys that this map is the authoritative source for residency claims.

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 zero-parameter tool, this is mostly adequate: it identifies the returned content and scope. However, without an output schema or usage guidance, an agent is left to guess the exact return structure and when to choose this tool over resolve_jurisdiction.

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?

The input schema has zero parameters, so the baseline of 4 applies. No parameter documentation is needed, and the description adds no parameter semantics because there are none to describe.

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 clearly states that the tool returns the eighteen jurisdictions where GSC Carriers are resident, along with each jurisdiction's serving Azure region. It is distinct in scope from sibling tools like resolve_jurisdiction, though it relies on the tool name for the explicit 'list' 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?

No guidance is given about when to use this tool versus alternatives like resolve_jurisdiction or find_carriers. The line 'Residency is the checkable claim' hints at a use case, but it does not explicitly state when to call this tool or when to prefer a sibling.

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