search_products

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

No annotations are provided, so the description carries full burden. It states it performs a search and returns fields, but does not disclose behavioral traits such as pagination behavior, sorting defaults, case sensitivity, rate limits, or authentication needs. The read-only nature is not explicitly asserted.

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 with no fluff. The purpose is front-loaded: 'Search the Cart product database across all tracked stores.' Each sentence contributes value and the structure is efficient.

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 7 parameters, no output schema, and no annotations, the description is brief. It covers basic functionality and return fields but omits details like pagination defaults, sorting behavior, error handling, and currency handling. Adequate but incomplete for a moderately complex 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 baseline is 3. The description (e.g., 'Filter by keyword, price range, and currency') maps to existing schema descriptions but adds no new meaning or context beyond what the schema already provides for each parameter.

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 verb 'Search' and the resource 'Cart product database across all tracked stores.' It specifies filtering capabilities and return fields, making it distinct from siblings like 'search_stores' (which searches stores) and 'get_product' (single product).

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 implies use for broad product search but does not explicitly state when to use this tool versus alternatives like 'search_stores' or 'get_product.' No exclusion criteria or when-not-to-use guidance is provided.

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