search_all_consignments

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

The description reveals that the tool fetches all consignments in parallel, which is a key behavioral trait. Without annotations, it partially covers safety and performance, but lacks details on rate limits, timeouts, or response format.

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. The first sentence states the core function, and the second provides a critical usage warning. Every word is essential.

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 is too brief given the tool's complexity (6 parameters, no schema descriptions, no annotations). It fails to explain how parameters work, what the output structure is, or how parallel fetching is handled, leaving the agent under-informed.

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 must compensate by explaining parameters. It mentions 'filters' but does not describe any of the six parameters (q, status, warehouse_id, etc.), offering no added meaning beyond their names.

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 verb 'Fetch', the resource 'consignments', and the scope 'across all pages in parallel'. This distinguishes it from the sibling 'list_consignments', which likely provides paginated results.

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 explicitly warns to 'ALWAYS use filters to narrow results', providing a critical usage guideline. However, it does not specify when to prefer this tool over siblings like 'list_consignments', leaving some ambiguity.

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