Get network product order

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial value beyond them: required scopes (networking:read vs networking:manage), the note that full/read defaults do not grant networking, and backend enforcement of ownership, feature availability and 2FA locks. It also decodes status transitions, which is real behavioral context.

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?

Purpose is front-loaded and every sentence carries useful state or auth information. The status-semantics sentences are dense but each earns its place; the brevity of 'paid_pending is not ready' is a minor stylistic jolt rather than waste.

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 single-parameter read tool with no output schema, the description covers the return semantics (paid_pending, manual_review, fulfilled with attachment status), the polling contract, and the authorization model. Nothing an agent needs to call or interpret it correctly is missing.

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 description coverage is 100% for the single order_id parameter, so the schema already documents format and constraints. The description refers to 'this order' but adds no syntax, ownership or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The opening sentence names a specific verb (Read) and resource (an owned common-checkout order) and states exactly what is retrieved: payment and fulfilment state. This implicitly separates it from sibling search/order tools like find_network_product_order and order_network_product without needing their 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?

It gives concrete operational guidance — keep polling a paid_pending order without re-purchasing or retrying, and route manual_review / network_product_stock_reconciliation_required to operator review. It does not, however, explicitly name alternatives (e.g., find_network_product_order or list_network_products) or state when this tool is the wrong choice, so it falls short of full routing guidance.

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