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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the resource scope and the hosted/dedicated distinction, but says nothing about pagination, filtering behavior, or ordering that the schema doesn't already imply.

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?

A single tight sentence that front-loads the verb+resource and defers the qualifier. No filler or redundancy.

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 values need no explanation, and annotations cover safety. However, for a list tool with a search parameter and a result cap, the description does not address filtering, pagination, or how this differs from pf_list_cloud_router_connections.

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 coverage is 50%: 'fields' and 'max_items' are documented in the schema, while 'q' is undocumented and 'kind' is carried by its enum. The description restates the hosted/dedicated values in prose, adding mild value but nothing about what 'q' searches, so baseline 3 is appropriate.

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 ('Layer-2 cloud connections'), plus the domain scope (AWS, Azure, Google, Oracle, IBM) and the two variants (hosted/dedicated). It is clear on its own, but does not explicitly differentiate itself from the close sibling pf_list_cloud_router_connections, 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?

There is no when-to-use guidance, no exclusions, and no named alternative despite a very similar sibling (pf_list_cloud_router_connections). The agent must infer context purely from the tool name.

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