clear_static_nat

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates remote state; the description adds the useful scoping detail that removal is keyed by internal IP (i.e., potentially all rules for that IP), which goes beyond the annotations. It stops short of stating whether the operation is irreversible, idempotent, or requires elevated auth, and destructiveHint=false sits somewhat awkwardly with a verb like "Remove".

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 front-loaded sentence with no filler. The trailing parenthetical "(nat/clear_static_nat)" merely restates the tool name/endpoint and earns little, keeping it just short of a 5.

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?

There is no output schema, so return values need not be explained, and annotations carry the safety profile. Still, for a state-mutating removal keyed by IP, the description leaves unclear whether one rule or all matching rules are deleted and what failure looks like, which is a real gap for an agent deciding to call it.

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 both `ip` and `confirm` are already documented; baseline is 3. The phrase "by internal IP" adds modest value by clarifying that the IP is the selector for which rules are cleared, but the description adds nothing about the mandatory `confirm` flag or the address format.

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?

Clear verb+resource+scoping: "Remove ... static NAT forwarding rules by internal IP". An agent knows exactly what is affected and how it is keyed. However, it does not distinguish itself from the near-identical sibling remove_static_nat (or drop_nat), so the selection decision is left ambiguous.

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 word "stale" hints at the intended scenario (cleaning up obsolete rules), which is a weak implied usage signal. There is no explicit when-to-use, no when-not-to-use, and no routing to remove_static_nat or drop_nat, which is exactly what this tool's closest siblings would require.

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