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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the 100-item result cap and notes it surfaces a low-stock flag, but the output schema already defines returned fields, so the incremental behavioral disclosure is modest.

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?

Three short sentences: trigger first, then what is returned, then the exclusion. No filler and the most decision-relevant information is front-loaded.

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?

With rich annotations, full schema coverage and an output schema, the description only needs to establish purpose and scope, which it does. The one gap is that it does not point at the mutation sibling (set_inventory_quantity) or explain pagination beyond the 100-item ceiling, which is minor given the structured fields.

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 100% and all four parameters (limit, search, businessId, lowStockOnly) are documented there, including the default of 50 and the 100 maximum. The description adds no parameter-level meaning beyond restating the 100-item return cap, so the baseline of 3 applies.

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 states a concrete verb and resource ('how much of a material, product or supply a business has left in stock') and describes the returned fields (unit, quantity, minimum, low-stock flag). The closing exclusion ('Not for the prices a business charges') separates it from pricing-oriented siblings such as list_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?

It gives an explicit triggering situation ('when someone asks how much ... is left in stock, or what is running low') and one clear out-of-scope case (prices). It does not name the natural counterpart set_inventory_quantity or list_products as alternatives, so the when-not guidance is incomplete rather than exhaustive.

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