search_orders

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

No annotations are provided, so the description carries the full burden. It conveys that the tool searches by order number and supports exact matching, but it does not disclose behavior such as whether multiple results are returned, pagination, or error handling. The output schema exists but is not detailed in the description.

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 extremely concise with two sentences. Every word adds value: it names the action, resource, and key parameter behavior. No wasted content, front-loaded with the purpose.

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?

Given the tool's simplicity (2 parameters, no nested objects, output schema exists), the description is adequate but lacks details about search behavior (e.g., multiple results, pagination). It is minimally complete for an agent to understand the core functionality, but could be improved.

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%, so the description must compensate. It explains the 'exact' parameter (exact match recommended) and implies the use of 'order_number' by stating the search is by order number. This adds meaningful context beyond the schema alone, though format details for order_number are omitted.

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 'Search orders by order number.' This is a specific verb and resource, and it distinguishes from sibling tools like list_orders (which lists all) and get_order (which retrieves a single order by ID). The search is specifically by order number, not other criteria.

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 recommends using exact=True for an exact match, but it does not explicitly state when to use this tool over alternatives or when not to use it. Context is implied but not fully articulated; no exclusions or alternative tool references are provided.

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