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

Adds substantial context beyond the annotations: no automatic pagination or retries, the need to request the next page when full_page is returned, and concrete per-user (3/s) and site-wide (10/s) rate limits. This is exactly the operational detail an agent needs to call it correctly.

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?

Four dense sentences, each carrying a distinct fact (what's returned, filter/sort availability, pagination behavior, rate limits) with the payload front-loaded. No filler.

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 does the work of explaining the result shape (page contents, full_page continuation) and the operational envelope. Only the page/limit parameter meanings are left implicit for an agent to infer.

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 50% and the description only restates that filter/sort are 'Infoplus expressions' without adding syntax or field guidance beyond the schema's own description and example. Page and limit are undocumented in both places, though their names, defaults and bounds are self-explanatory.

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 and resource plus the returned dimensions: stock quantities, lots, warehouse location IDs. It is clearly a paged search, distinct from infoplus_get_inventory_detail, though it never names that sibling to cement the distinction.

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?

Implies usage through 'Optional Infoplus filter and sort expressions' and the pagination note, and warns about rate limits, but never states when to choose this search over infoplus_get_inventory_detail or the other search_* siblings. No explicit exclusions.

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