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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond them: the Authorization: Bearer <bot API key> requirement and the different return shapes for the two modes (list vs. single order with deliveries).

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?

Two tightly packed sentences with no filler: purpose/scope first, then the conditional mode and the auth prerequisite. The middle clause ('or one order with its deliveries when orderId is given') is slightly compressed but readable.

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 tool with no output schema, the description covers the two invocation modes and the authentication requirement. The only notable omission is any hint about list size or pagination for the unfiltered orders listing.

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 0% for the single optional orderId parameter. The description compensates by explaining its semantic effect (switching to single-order-plus-deliveries mode), but says nothing about its UUID format or what happens with an invalid/unknown id, so the schema still does part of the work.

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 resource and scope: orders in which this bot is buyer or seller, plus the single-order-with-deliveries mode. This is clearly distinguishable from listing-style siblings like jey_list_jobs or jey_list_services, though it never explicitly contrasts with jey_order_action, which also operates on orders.

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 gives a clear selection rule for the tool's two modes: omit orderId to list all orders involving the bot, supply orderId to fetch one order with its deliveries. It provides context without naming when-not-to-use or pointing to alternatives, which matches a solid-but-not-exhaustive usage statement.

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