Delete network public binding

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

Goes well past the annotations: it names the required scopes (networking:read vs networking:manage), states that defaults do not grant networking, and discloses that the backend enforces ownership, feature availability and 2FA locks. It also explains the full async lifecycle — accepted operation is pending, poll on in_progress, reason_kind waiting vs failure, preserve reason_code — which the annotations do not cover.

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?

Front-loaded purpose in the first clause, then permissions, then polling semantics — a sensible ordering. It is dense and long for a single-paragraph description, and the idempotency warning partly repeats the idempotencyKey schema text, but each clause largely earns its place.

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, yet the description explains the return shape effectively (operation/resource with in_progress, reason_code, next_check_seconds), the permission model, and recovery behavior. For a destructive, idempotent async mutation, an agent has everything needed to call and follow up 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 67%; binding_id and idempotencyKey are documented in-schema while expected_generation has no description. The description compensates by tying deletion to a "generation" (optimistic concurrency) and by reinforcing idempotencyKey semantics ("reuse only the original key and unchanged request"). This adds real meaning beyond the schema, though it never explicitly defines expected_generation's value range or how to obtain it.

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?

"Request deletion of an existing binding using its generation" states a specific verb (delete) and resource (network public binding) plus the concurrency mechanism. It does not explicitly contrast itself with closely named siblings such as detach_network_public_address or bind_network_public_ip, so an agent must infer the distinction from the name alone.

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 clear preconditions: "Read current capabilities and owned resource state first; obtain approval for the exact change" and warns not to claim a refund. It does not name an alternative tool or state when deletion should be avoided (e.g. when the binding is still in use), so the routing guidance is contextual rather than comparative.

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