Get network public binding

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description goes well beyond them: required scopes (networking:read / networking:manage), the warning that full/read defaults do not grant networking, and backend enforcement of ownership, feature availability and 2FA locks. This is meaningful pre-call context for a read tool.

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 the core purpose and then the polling trigger, negatives, and auth constraints. Every sentence carries distinct information, though the auth sentence ('for reads or changes') is slightly dense and marginally redundant on a read-only tool.

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 compensates by naming the returned fields, and it covers auth, ownership and operational routing. An agent has everything needed to invoke and interpret this call 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?

Only one parameter, and schema description coverage is 100%, so the schema already defines binding_id in full (UUID pattern, length). The description adds no syntax or constraint detail beyond implying ownership, so the baseline 3 applies.

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 (read) and resource (one existing owned public binding), plus exactly what it returns: generation, state and assigned address. It also explicitly separates itself from get_network_public_address ('Existing bindings are distinct from purchasing an account public address') and from the operation-fetching siblings.

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 a concrete when-to-use trigger ('Poll this resource after bind, move, forward or delete') and an explicit negative routing rule ('public-binding operation IDs are not accepted by get_networking_operation or get_network_appliance_operation'). An agent can pick this tool versus its nearest alternatives without inference.

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