Delete Port Forwarding Rule

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not state that the operation is irreversible, whether a confirmation is required, whether dependent resources are removed, or what the response contains — critical omissions for a destructive delete tool with no annotation coverage.

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?

The description is extremely short, but this reflects under-specification rather than disciplined conciseness. There is nothing to front-load because the entire description is a copy of the title.

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?

Although an output schema exists (so return values need not be described), this destructive tool has no annotations, no parameter documentation, and no usage context. For a delete operation with a required identifier, the description is wholly inadequate.

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 0% and the single parameter rule_id has no schema description, so the description must compensate — and it does not. It never mentions the rule_id parameter, its expected format, or where the identifier can be obtained.

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 is a verbatim translation of the tool name ('delete port diversion'/'delete port forwarding rule'), so it adds no information beyond what the tool name already conveys. While the verb+resource pairing ('delete' + 'port forwarding') is technically interpretable, it is a tautological restatement rather than a distinguishing statement against siblings like delete_domain_forwarding_rule.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no warning about the destructive operation. The agent receives nothing about obtaining a valid rule_id beforehand (e.g., via list_port_forwarding_rules) or how deletion interacts with add_port_forwarding_rule.

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