Quote network public address

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

Goes well beyond the annotations: permission scope (networking:read vs networking:manage, networking:order, spend caps), 2FA locks, idempotency-key reuse rules, never-auto-retry, and detailed polling semantics (poll on in_progress, reason_code/reason_kind, next_check_seconds). Annotations are not contradicted; 'no charge' plus openWorld/idempotent hints are consistent with the quoted/preflight behavior described.

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?

It is a dense run-on block that mixes purpose, auth, polling, idempotency, payment and catalog selection into long semicolon-chained sentences, with generic filler like 'Read current capabilities... first.' Only the first clause is front-loaded; the rest is hard to scan.

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?

For a complex, paid, permissioned, asynchronous quote operation with no output schema, the description supplies the full lifecycle: prerequisites, approval, idempotency, polling, failure interpretation and the pending-vs-ready distinction ('Payment acceptance is not resource readiness'). Nothing critical is left unstated.

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%, so the baseline is 3, but the description adds real meaning: network_id preflights attachment limits before payment, and the idempotency key must be identical across quote and confirmation. That extends the terse schema descriptions rather than merely restating them.

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 ("Quote a new paid public address") and scopes it (common checkout, no charge), which distinguishes it from quote_public_address_renewal and order_network_product. It names order_network_product as the confirmation path, but does not explicitly contrast itself with the other quote_* siblings, so it stops just short of full sibling differentiation.

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 routing guidance: prepare_after_payment=true, confirm via order_network_product, read capabilities/owned state first, obtain approval before the change. It clearly establishes preconditions but never states when-not to use it (e.g., vs. a renewal or renewal-quote path).

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