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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description goes well beyond that by disclosing immediacy ("machines with the group lose it at once"), the platform's automatic public-URL port opening behavior across all groups present at that moment, the fact that later-attached groups are unaffected, and concrete failure modes (URL goes offline, port 22 removal ends external SSH).

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 core action and its immediate consequence are front-loaded, and the confirmation instruction comes early. The public-URL passage is the longest part but carries genuine hazard information rather than filler, though it could be tightened.

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 an output schema present and annotations covering the safety profile, the remaining burden is hazard disclosure and confirmation policy — both covered thoroughly. An agent has everything needed to call this correctly and to warn the user about SSH or URL loss.

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 100% and the schema's own id description already says it comes from a group's rules in list_security_groups, so the description's id-sourcing sentence largely repeats structured data. Baseline 3 applies; no additional format or validation meaning is added.

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 opening clause states a specific verb and resource with precise scope: "Permanently removes one rule from a security group." That cleanly separates it from add_security_group_rule (adds a rule) and delete_security_group (removes the whole group) without needing to name them.

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?

It gives an explicit precondition — "Ask the user first" — and tells the agent where to source the required id ("Get the rule id from list_security_groups"). It does not explicitly say when to prefer this over add_security_group_rule or delete_security_group, but the destructive framing makes the intended context clear.

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