sku_quantity_keep_pick

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

With no annotations, the description's statement that it 'get's quantity' suggests a read operation, but it does not disclose any behavioral traits such as handling of null SKU, error cases, or side effects.

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 sentence, directly stating the purpose with no filler or redundant information.

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?

While an output schema exists, the 0% parameter schema coverage and lack of annotations leave gaps. The description is complete for its simplicity but does not cover parameter behavior or potential edge cases.

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%. The description mentions 'sku' implicitly but does not explain the parameter's meaning, constraints, or the effect of the default null value. It adds minimal value beyond the schema.

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 uses a specific verb 'Get' and clearly identifies the resource as 'quantity reserved for outgoing order picks (not available for sale)', distinguishing it from sibling tools like sku_quantity_available.

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 implies the tool is for quantities reserved in picks, but does not explicitly state when to use it over siblings, nor provide any when-not-to-use guidance.

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