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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. The description adds only that the listing spans five clouds and connection facets; it says nothing about pagination, truncation at max_items, or ordering that would go beyond the structured fields.

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?

One sentence, front-loaded with the verb and resource, with the scoping detail in a single parenthetical. No filler and nothing to remove.

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?

An output schema exists, so return structure need not be explained, and annotations cover the safety profile. For a three-parameter read-only list tool this is essentially sufficient; only an explicit disambiguation from sibling list tools 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%, so each parameter (fields, max_items, cloud_router_circuit_id) is already documented in the schema; baseline 3 applies. The description's "for one router" loosely maps to cloud_router_circuit_id and "ports, IPsec" loosely maps to fields, but adds no syntax or format detail beyond the schema.

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 (List) and resource (Cloud Router connections), plus what a connection spans (AWS/Azure/GCP/Oracle/IBM, ports, IPsec) and the scope (account-wide or one router). It does not address the nearby sibling pf_list_cloud_connections, which is the main lexical ambiguity an agent would face, so it stops short of a 5.

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?

"across the account or for one router" implies the two usage modes and signals that filtering is optional, but there is no explicit when-to-use, when-not-to-use, or named alternative to pf_list_cloud_routers / pf_list_cloud_connections. Usage is inferable but not stated.

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