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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description goes further, disclosing the required permission (firewall:write), the account/MCP-key prerequisite, and — importantly — the risky default source of 0.0.0.0/0. It stops short of describing the effect of the change or failure modes.

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?

Three tight clauses with zero filler: the action, the port syntax, and the permission/account requirements. The most decision-relevant information (protocol and default source exposure) is front-loaded.

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?

With no output schema and a low schema coverage, the description still supplies the prerequisites, permission, and key parameter semantics. It omits the success/return behavior of a mutation, but the annotations cover the safety profile, so an agent has enough to call it correctly.

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 29%, so the description must carry more weight. It usefully explains port syntax (single '8080' vs portRangeMin/portRangeMax) and the source-CIDR default (0.0.0.0/0), which the schema does not. But it is silent on direction and ethertype, leaving two of seven parameters undocumented in both places.

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 ('Opens') applied to a precise resource (a port range/icmp on a ready server as a firewall rule). The 'firewall rule' framing cleanly distinguishes it from gpucloud_delete_firewall_rule and gpucloud_list_firewall_rules without needing the schema.

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 'on a ready server' phrasing implies the prerequisite that the server must be running, and the permission string signals the required scope. However, it never explicitly states when to use this versus the delete/list firewall siblings, leaving the routing to inference.

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