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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses that sign-in is required, that the result is rendered as a status card with a progress stepper and sometimes a map, and that the tool should be called again to refresh live data. These are meaningful operational details not present in 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 purpose is front-loaded and the description is information-dense, but the first sentence is a long run-on with nested parentheticals and an exhaustive list of returned item fields. Because an output schema exists, some of that return-field detail is redundant, though the overall structure remains usable.

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 one-parameter read-only tracking tool with an output schema, the description covers the essential context: what is tracked, how to pass or omit the order id, authentication, refresh behavior, and when a map is available. Nothing critical for correct invocation 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 coverage is 100%, and the schema already documents that omitting orderId tracks the most recent active order. The description repeats this behavior but adds no syntax or format detail beyond the schema; the casing mismatch between 'order_id' and 'orderId' is a minor inconsistency rather than added 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?

The description gives a specific verb and resource — 'Track a Lezzoo order live' — and immediately clarifies the live-active-order scope versus historical orders. It is detailed enough that an agent can distinguish it from order-history or checkout-review tools without opening the schema.

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 clearly explains the two invocation modes: pass an order_id, or omit it to track the customer's most recent active order. It also states sign-in and read-only requirements, but it does not name alternatives or when-not-to-use conditions, so it falls short of full alternative routing guidance.

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