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

Goes well beyond the readOnly/idempotent annotations: it discloses the paging budget (up to 10 inventory pages and 5 catalog pages, max 15), the truncation behavior of items vs matched, and that out-of-catalog barcodes are excluded and surfaced in notInCatalog. This is exactly the kind of API-level behavior an agent cannot infer from structured fields.

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?

Front-loads the core definition and then layers threshold logic, exclusion rules, and API budget. Dense but every sentence carries information; a few clauses (e.g. the parenthetical page math) could be trimmed.

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 no output schema, the description compensates by defining the returned fields (matched, items, notInCatalog) and their relationship. Combined with the call-budget disclosure, an agent has everything needed to call and interpret this 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 already 100%, so the baseline is 3, but the description adds meaning beyond it by explaining the interaction between threshold defaults, per-row ReorderLevel fallback, and how limit truncates items while matched stays complete. It reinforces rather than duplicates 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?

Opens with a precise verb+resource+condition: retail products in the current catalog at or below their reorder point. It also distinguishes itself from the sibling inventory tool by noting 'Inventory has no category filter', so an agent can tell it apart from get_products_inventory.

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?

Gives clear operating guidance: use 'matched' for the true count rather than counting returned rows, and note that no category filter exists (pointing implicitly at other catalog tools). It stops short of naming a specific alternative tool or stating an explicit when-not-to-use condition.

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