search_serial_number

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the search works by fetching orders and can be slow at high volume, and that it returns order details when found. It omits other behavior an agent needs: what happens on no match, whether multiple matches are possible, and any auth scoping.

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?

Three short sentences with purpose front-loaded, then return behavior, then a clearly flagged warning. No filler, though the redundant 'serial number/serial number' phrasing is a minor wobble.

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 two-parameter search with no output schema, the description covers purpose, result shape, and a performance caveat, which is reasonably complete. It still leaves gaps about match multiplicity and what the returned order details contain, which matter when no output schema exists.

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%: both serialNumber and maxOrders (with default 500 / max 2000) are already documented in the schema. The description adds only indirect context via the performance note, which loosely relates to maxOrders, so the baseline of 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?

States a specific verb and resource ('Search for a serial number') scoped to a specific domain ('across fulfilled sales orders') and notes the return ('order details if found'). However, it does not differentiate from the many sibling serial tools (list_serial_numbers, get_sales_order_serials, list_all_serials), so an agent cannot tell why this one is chosen over those.

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?

There is no explicit guidance on when to use this versus get_sales_order_serials, list_serial_numbers, or list_all_serials. The performance warning implies caution for large volumes but never names an alternative tool or condition that would route the agent elsewhere.

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