Bind network public IP

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

Adds substantial context beyond the annotations: exact scope requirements (networking:read vs networking:manage, with full/read defaults not granting networking), backend enforcement of ownership, feature availability and 2FA locks, and the crucial warning that an accepted operation is pending rather than proof of connectivity. It also fully specifies the polling contract (in_progress/reason_kind/reason_code, next_check_seconds) and the no-auto-retry policy on transport uncertainty.

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 with purpose and the 'does not purchase' scope, then moves to prerequisites and the polling protocol; every sentence carries operational weight. It is dense and long, but for a tool with no output schema the polling/reason_code detail is not filler.

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, the description carries the full burden and does: it describes the returned operation/resource, the in_progress flag, reason_kind/reason_code semantics, next_check_seconds, and the failure condition. Combined with auth scopes and idempotent recovery rules, an agent has everything needed to invoke 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 75%, so the schema already documents binding_id, private_port_id and idempotencyKey. The description reinforces idempotency-key preservation and body-unchanged recovery, but adds nothing for expected_generation (optimistic-concurrency semantics are left unexplained), so it only marginally exceeds the schema.

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+resource (bind a floating public binding to a private port) and scopes it with 'already reserved' and 'does not purchase an address,' which separates it from purchase/attach siblings. It stops short of naming an explicit alternative tool, so it is clear but not fully sibling-differentiating.

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?

Gives concrete preconditions: read capabilities and owned resource state first, obtain approval for the exact change, and the operation only applies 'when supported.' No sibling tool is named as an alternative, but the when-to-use context is explicit and actionable.

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