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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the underlying endpoint (GET /orders/search), which is modest extra context. It does not disclose whether at least one filter is required, how results are sorted, or default/maximum page size behavior beyond what the schema states for per_page.

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 short sentences, with the searchable facets front-loaded and the API endpoint appended as a compact reference. No filler or redundancy.

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 read-only search tool with no output schema, the description covers what can be filtered but leaves the result shape, ordering, and pagination semantics unaddressed, and gives no signal on how many of the eight optional filters to combine. Adequate but with clear gaps.

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 63%, so most parameters are documented, and the description enumerates the searchable facets, which helps prioritize filters. However, 'customer' is ambiguous against the integer customer_id, status values are left unspecified with no enums anywhere, and pagination parameters are not mentioned in the description.

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 (search) and resource (orders) plus the facets it queries, so the operation is unambiguous. It stops short of distinguishing itself from close siblings such as locate2u_find_order, locate2u_get_order, and locate2u_list_orders_created, which an agent could easily confuse with a filtered search.

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 listing of queryable facets implies that this is the multi-filter lookup tool, but there is no explicit when-to-use guidance and no mention of the alternatives (find_order for a single lookup, list_orders_created for recent orders). The agent must infer the routing decision from sibling names alone.

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