List port forwarding rules

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered and the description carries little burden. The description adds only the scoping fact that results are bound to a single public IP; it says nothing about result ordering, empty-result behavior, or pagination semantics beyond what the schema already encodes.

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 sentence with zero filler, and the resource and scope are front-loaded in the first few words. It is efficient rather than padded, though its brevity leaves room for one more clause of routing guidance at no structural cost.

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 read-only list endpoint with rich annotations and full schema coverage, the definition is adequate but minimal: it does not mention that results are paginated or how to page through large rule sets, which the schema only implies via page/pageSize. Nothing is misleading, but nothing anticipates the agent's need to iterate pages.

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 ipId, page, and pageSize are already fully documented, including the 1-indexed paging and the 500-item cap. The description's phrase 'on a public IP' merely reinforces the ipId parameter and adds no format or behavioral detail 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?

States a specific verb ('List') and resource ('port forwarding rules') plus the scoping entity ('on a public IP'), so an agent can distinguish it from list_firewall_rules, list_egress_rules, and list_load_balancer_rules. It stops short of naming any sibling explicitly, which is the only thing separating it from 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 or when-not-to-use guidance and no alternative named. An agent must infer from the sibling list that this tool is the per-IP rule lister rather than the firewall or load-balancer equivalents, and nothing tells it whether a public IP must already exist or how to obtain the ipId.

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