search_all_warehouse_pickings

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

The description reveals the parallel fetching behavior, but lacks details on whether the operation is read-only, resource implications, or any side effects. Since no annotations are provided, the description carries full burden and is insufficient.

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 consists of two concise sentences with no unnecessary words. It front-loads the core purpose and adds a critical usage hint.

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?

Despite having an output schema, the description fails to document parameters or explain the tool's behavior in sufficient detail for a 6-parameter tool. It omits important context about page size, result format, and performance considerations.

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?

With 0% schema description coverage, the description does not explain any parameter meanings. It only says to use filters, without describing the purpose of 'warehouse_id', 'type', 'status', 'include', 'start_create_date', or 'end_create_date'. The parameter 'include' is particularly ambiguous.

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 the action ('Fetch ALL warehouse pickings across all pages in parallel'), specifying the resource and scope. It distinguishes from the sibling 'list_warehouse_pickings' by emphasizing 'ALL' and parallelism.

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 advises to 'ALWAYS use filters to narrow results,' which is a helpful guideline. However, it does not explicitly state when to use this tool versus the sibling 'list_warehouse_pickings' or other alternatives.

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