sku_quantity_available

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

No annotations are provided, so the description must disclose behavioral traits. It only states the output is 'available (sellable) quantity' but omits details like authorization requirements, rate limits, or what happens if the sku parameter is null or invalid.

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 that front-load the key information. No extraneous words or repetition.

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?

Given the low schema coverage and lack of annotations, the description is too brief. It does not explain the sku parameter's role, the default behavior when sku is null, or the output structure despite an existing output schema. More context is needed for reliable use.

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?

The single parameter 'sku' has a schema allowing string or null, but the description does not explain its meaning, format, or how it affects the result. With 0% schema coverage, the description should compensate but fails to add 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 clearly states the tool's purpose: 'Get AVAILABLE (sellable) quantity.' It specifies the resource (sku quantity) and the condition ('sellable', 'can be sold NOW'), distinguishing it from sibling tools like sku_quantity_in_warehouse or sku_quantity_wait_incoming.

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 usage for obtaining sellable quantity but provides no explicit guidance on when to use this tool versus alternatives (e.g., other sku quantity tools). No examples or when-not-to-use advice is given.

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