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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond annotations: every export includes a provenance header with source URLs and mirror time, and it reports rule cost. No contradiction with 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 core information is dense and mostly front-loaded, but the 'FIRST CALL, needs nothing: {"name":"whoami",...}' prefix is confusing in a tool description and interrupts the main purpose statement. The rest is reasonably concise.

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 tool with 0 required parameters and a 100%-covered schema, the description is nearly complete: it lists formats, uses a representative example, and explains provenance and cost behavior. The main missing piece is explicit guidance on what the returned text/header looks like, but the provenance statement partly covers that.

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%, so the schema already documents all five parameters and their enums/defaults. The description adds only a representative example and format-name context, which is useful but not required for parameter understanding.

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 and resource: 'Turn a set of operators into a config you can paste', and enumerates the concrete output formats (nginx, Apache, HAProxy, Cloudflare, ipset, Caddy, CIDR). This clearly separates it from sibling verification/lookup tools.

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 gives clear context for when the tool applies (any need for paste-ready allow/deny config), reinforced by a concrete example. It does not explicitly state when not to use it or name an alternative, and the opening 'FIRST CALL... whoami' prerequisite is cryptic.

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