search_orders

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

No annotations provided, so the description bears full burden. It mentions hybrid supports exact tracking/order search and fuzzy recipient name, but does not disclose pagination behavior, default ordering, or read-only nature. Schema covers parameter descriptions, but description lacks behavioral context beyond basic filters.

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 sentences: first states core function and filters, second provides essential usage rule. Extremely concise with no wasted words, front-loaded with key information.

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?

While parameter descriptions are complete in schema, the description lacks information about return format (list of orders or details?), sorting, and handling of empty results. Given no output schema, more completeness would be beneficial. However, sibling tool get_order_detail covers single order details.

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%, baseline 3. The description adds critical usage rule for the hybrid parameter that is absent from the schema description. This provides meaningful extra guidance beyond what the schema alone offers.

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 it searches order lists with filters (status, store, date, keyword). The distinction from sibling tools like get_order_detail (single order) and search_shipments (shipments) is clear.

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?

Explicitly instructs to use the hybrid parameter when the user provides ID-like content (order number, tracking number, etc.), providing clear when-to-use guidance and differentiating from a plain keyword search.

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