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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds that no authentication is required and identifies the underlying GeoServer WFS data source, which are practical operational details beyond the annotations. There is no contradiction with the annotations.

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 three concise sentences with no filler: function and output, downstream usage, and data source/auth context. The most actionable information is front-loaded.

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 simple tool with two optional parameters, rich annotations, and an output schema, the description provides sufficient context: what is listed, how the results should be used, where the data comes from, and that no auth is required. Nothing necessary for correct invocation 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 description coverage is 100%: `name` and `limit` are fully documented with constraints, defaults, and filter semantics. The description only restates the optional name-substring filter and does not add meaningful parameter information beyond the schema, so the baseline 3 applies.

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 states a specific verb ('List'), a specific resource ('countries covered by Malaria Atlas Project admin boundaries'), and the exact returned fields (ISO3/ISO2 codes and name), plus an optional substring filter. This clearly distinguishes it from the sibling malaria-atlas data tools, which consume country codes rather than list them.

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 description explicitly instructs the agent to use the returned ISO code as the `country` filter for other malaria-atlas tools, defining its role in a downstream workflow. It does not explicitly spell out when not to use it versus alternatives, but the reference-vs-data distinction is clear from the wording.

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