find_inventory

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

Annotations indicate a safe read-only operation (readOnlyHint=true). The description adds behavioral context: returns up to 'limit' items, specifies the structure of item cards, and notes ranking preference for verified brands, referencing droplinked's KYB cascade. No contradiction with annotations.

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 is a single paragraph that front-loads the main purpose and then details parameters and return fields. It is well-organized but slightly lengthy; however, every sentence adds value.

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?

For a tool with no output schema or defined parameters in schema, the description covers input semantics, output format, and ranking suggestion. It lacks details on default limits or pagination, but overall it is quite complete.

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 input schema has no properties, yet the description fully defines parameters (query, brandSlug, country, currency, etc.) with clear meanings. It compensates entirely for the empty schema, adding necessary semantics.

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: 'Discover droplinked inventory (SKU-level) matching a free-text query and/or filters.' It specifies the verb 'discover' and the resource 'inventory', and distinguishes from siblings like find_merchant by focusing on SKU-level inventory with specific filters.

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 explicitly instructs users to provide at least one of 'query' or 'brandSlug' and lists optional filters. However, it lacks explicit guidance on when NOT to use this tool or direct alternatives among siblings, such as when to use find_affiliate_programs instead.

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