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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new context: a connected Forthcast store is required and the assistant will prompt for sign-in, which is exactly the kind of prerequisite an agent can't 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?

Two sentences, no redundancies, with the use case and examples front-loaded before the auth prerequisite. Every clause carries 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?

With an output schema present, return values need no explanation, and the description covers purpose, filters, and the auth prerequisite. The only gap is any hint about result ordering or how the bounded limit interacts with the merchant's request, which is minor for a read-only list tool.

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%, so the schema already documents limit, vendor, urgency, and supplier, including the urgency enum values. The description only restates the filter axes and adds no syntax, ordering, or defaulting nuance beyond the schema — the baseline 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 specific verb+resource ('bounded list of their items') and enumerates the three filter dimensions (urgency, supplier, Shopify vendor). It implicitly distinguishes itself from singular/aggregate siblings like get_inventory_item and get_inventory_overview via the word 'list', but never names an alternative explicitly.

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 a clear triggering condition ('Use this when the merchant wants a bounded list...') and concrete examples ('all excess items or a supplier's critical SKUs'). It does not state when NOT to use it or which sibling to pick for aggregate/single-item questions, so a 5 isn't earned.

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