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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description only needs to add extra context. It adds the 'authoritative' source-of-truth claim, the return structure (line-item breakdown and order rollup), and the conditional StarShipit summary ('where available'). It does not mention the customer_email identity requirement, but that is captured in the schema's parameter description.

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?

The description is three concise, purposeful sentences: the first defines the return structure, the second lists the state enum, and the third captures the shipping-summary caveat. Every sentence earns its place with no filler or repetition of schema fields.

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 sufficiently sketches the response: per-line-item breakdown, order-level rollup, a complete state list, and an optional shipping summary. It relies on the schema for the required email and identity-match rules, and it does not discuss pagination or error conditions, but the moderate complexity of the tool does not demand much more.

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%, and all four parameters—order_id, order_name, line_item_id, and customer_email—are clearly documented, including the required identity-match constraint. The tool description adds no parameter-specific detail beyond the per-line-item context, but the schema already carries the burden, so a baseline 3 is 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 description clearly identifies an authoritative order-status resource with per-line-item and order-level rollup views, and enumerates the possible states. It distinguishes itself from general order-status and other fulfilment sub-tools by highlighting the line-item breakdown and StarShipit shipping summary, though it uses a noun phrase rather than a strong verb and offers no direct sibling comparison.

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?

Usage context is implied by the name and the per-line-item/order-level focus, but there is no explicit guidance on when to use this tool over alternatives like vivid_order_status, vivid_fulfilment_shipping, or vivid_fulfilment_production_stage. No exclusions or situational notes are provided.

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