Order network product

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

Annotations only give readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true; the description adds a great deal beyond that: permission scoping (networking:manage vs networking:read, full/read defaults not granting networking), spend caps and enabled-paid-operations gates, ownership/2FA enforcement, async pending semantics with reason_code/reason_kind/in_progress handling, and 'never automatically retry' recovery rules. Minor tension: the annotation says idempotentHint=false while the description leans heavily on idempotency-key deduplication, though this is arguably consistent (key reuse is mandated, not safe repetition) and not flagged.

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-loads the core action well, but the body is a dense wall that repeats itself: the permission model is stated twice ('Requires explicit networking:read ... full/read defaults do not grant networking' and later 'Requires full API access, networking:manage, enabled paid operations, networking:order and spend caps'), and 'An accepted operation is pending, not proof of connectivity' restates 'Payment acceptance is not resource readiness.' Useful content, but it would benefit from trimming.

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, high-risk, non-idempotent order-confirmation mutation with no output schema and no enums, the description covers the needed ground: prerequisites, quote/provenance requirements, approval and disclosure obligations, async polling semantics, failure vs pending discrimination, and recovery paths.

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%, and the description compensates for gaps: it identifies payment.payment as the account-balance method ID sourced from get_network_payment_methods ('do not guess it'), explains quote_id/quote_token provenance, and ties acknowledge_charge to disclosure of gross_amount in EUR before approval. It does not explain the secondary payment.paymentid field or the target.expected_generation semantics.

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 and resource: 'Confirm a common-checkout purchase from an approved exact quote.' This cleanly separates it from the sibling quote_network_product (which produces the quote) and renew_network_product (renewal path), so an agent can pick the right tool without opening schemas.

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?

Explicitly prescribes inputs (quote_id, quote_token, ORIGINAL idempotency key), names the alternative recovery path (find_network_product_order then poll get_network_product_order), and states a hard exclusion ('never buy a second copy'). It also names get_network_payment_methods as the source for the payment ID and warns against guessing.

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