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 that results include speed, status and POP, but says nothing about pagination, the interaction of max_items with truncation, or result volume — context an agent listing up to 5000 items would want.

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 with the operation and scope front-loaded and no filler. Every clause carries information.

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-value detail is unnecessary, and the readOnlyHint covers safety. The remaining gap is the absence of filtering guidance for the eight optional parameters, which the 63% schema coverage only partially fills.

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 only 63%, and the description names no parameters at all; the three undocumented booleans (is_lag, is_ptp, is_cloud) get no explanation anywhere. Worse, 'POP' is presented as a returned attribute rather than also being a filter parameter, which can mislead an agent about how to filter.

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 gives a specific verb ('List') and resource ('the account's ports') and enumerates the port subtypes (physical access, LAGs, cloud ports) plus returned attributes (speed, status, POP). It does not explicitly contrast with overlapping siblings like pf_get_port or pf_list_point_to_point, so it falls 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?

Listing is implied as the operation, but the description never states when to use this versus pf_get_port (singular) or the point-to-point/cloud-router listers. There are no exclusions or prerequisites, leaving routing to the agent's inference.

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