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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so no contradiction exists. The description adds minimal behavioral context by mentioning 'with their footprint', which hints at the returned shape, but it does not discuss pagination behavior, result ordering, or any operation-specific side effects.

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 one concise sentence, front-loaded with the core action and object, followed by a clear inclusion criterion and a note on output. It contains no filler or repetition.

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 tool is simple, read-only, and fully self-describing: the schema documents all four parameterschers, the annotations establish safety, and the output schema covers return values. The description provides the essential semantic filter, making the definition sufficient for reliable invocation.

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 100% parameter description coverage, so the description does not need to repeat those details. It also provides no additional parameter-level semantics beyond what the schema already contains. This matches the baseline for well-documented schemas.

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 a specific verb and resource: list insurance groups, and gives a concrete inclusion criterion (licensed entities in two or more countries). The phrase 'with their footprint' also clarifies the result contents; this differentiates it from single-entity tools like list_insurers and from the IAIS-specific list_iaigs.

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?

The inclusion criterion 'licensed entities in two or more countries' implies when the tool is appropriate, and the continent list suggests geographic scope. However, it does not explicitly state when to use list_groups instead of list_iaigs, list_insurers, or search_insurers, nor does it provide exclusion guidance.

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