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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds meaningful behavioral context by explaining what 'ready' means (printed and cut) and the specific location (Derrimut VIC), which helps the agent understand the tool's semantics beyond the annotations.

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 a single, front-loaded sentence that conveys the tool's essence without any redundant content. It earns its place by defining the tool's scope and readiness condition efficiently.

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 simple status query with comprehensive annotations and full schema coverage, the description adequately covers the tool's purpose and readiness definition. It omits return format details, but the 'whether' phrasing implies a boolean/status response, which is sufficient given the tool's simplicity and the presence of sibling tools for more detailed tracking.

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%, with detailed explanations for each parameter (e.g., customer_email being required for identity matching). The tool description itself adds no parameter-specific details, so the baseline of 3 applies since the schema does the heavy lifting.

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 states the tool's purpose: checking whether an order or line items are ready for pickup at a specific location, with a precise readiness criterion ('printed and cut, before dispatch'). This distinguishes it from sibling tools like vivid_fulfilment_order_status, vivid_fulfilment_production_stage, and vivid_fulfilment_shipping, which cover different aspects of fulfilment.

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?

The description provides clear context on when to use the tool (when checking pickup readiness at Derrimut VIC) and implicitly differentiates it from post-dispatch tools by noting 'before dispatch.' However, it does not explicitly name alternative tools or state when not to use it, so it falls slightly short of a perfect score.

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