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

The readOnlyHint annotation already covers safety, so the description adds useful behavioral detail by explaining the pagination cursor (next_after) and the returned dimensions (outlet, supplier, due/received dates, totals). It does not cover rate limits or response envelope details, but it exceeds the annotation baseline.

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 a single dense but front-loaded passage with no filler. The core purpose, type/status enumerations, pagination hint, and endpoint are all packed efficiently.

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 list tool with no output schema, the description provides enough context: what is listed, what filters exist, what fields are returned, and how to paginate. It lacks explicit sibling differentiation, but otherwise an agent has what it needs to call the tool correctly.

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 high (83%), but the description adds meaningful semantics beyond the raw enum labels: it maps SUPPLIER to supplier stock orders, OUTLET to transfers between outlets, and clarifies the status groups. It does not add much for after/before/page_size beyond what the schema already provides.

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 a specific verb and resource: it lists consignments and enumerates the four subtypes (SUPPLIER, OUTLET, STOCKTAKE, RETURN). It implicitly distinguishes itself from get_consignment by being a list operation, but it does not explicitly name siblings or contrast with list_consignment_products.

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 gives filtering context (type, status, outlet, supplier, dates) but never explicitly states when to use this tool versus get_consignment or list_consignment_products. Usage is implied by the listing/filtering language rather than stated as guidance.

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