search_products

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

With no annotations, the description must carry behavioral disclosure. It does disclose the returned fields and that login is not required, which is useful. However, it doesn't mention pagination behavior, result limits, or that this is a read-only operation, leaving some behavioral gaps.

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?

Three short sentences, each earning its place: what the tool does, what it returns, and what to do with the results. The most important facts are front-loaded and there is 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?

Given three parameters, no output schema, and no annotations, the description is fairly complete. It explains return values, the workflow with add_to_wishlist, and authentication. Minor omissions like pagination limits or default category behavior prevent a 5.

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 100%, so the baseline is 3. The description confirms 'query' means keyword and adds the purpose of the returned product IDs, but it doesn't add significant new meaning to 'page' or 'categoryId' beyond what the schema already documents.

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 ('Search'), a resource ('products on Webhallen'), and the result shape ('product list with IDs, names, prices, and stock info'). This clearly differentiates it from the sibling get_product, which implies fetching a single product, and from wishlist operations.

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 gives clear context: search by keyword to get product IDs for use with add_to_wishlist, and notes that no login is required. It doesn't explicitly list when not to use the tool, but the purpose is sufficiently scoped that an agent can infer the intended trigger.

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