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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool searches results, without mentioning any behavioral traits such as result limits, pagination, rate limits, authentication requirements, or whether the operation is read-only. This is a significant gap for a tool with no annotation support.

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, clear sentence that is front-loaded with the action and resource. It contains no redundant words and is appropriately concise for a simple search tool.

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 and no annotations, the description should clarify what the search returns and in what form. It only says 'results' without describing whether it returns product names, ratings, prices, or links. Additionally, it lacks usage context relative to sibling tools and gives no hints about how to deconstruct the response. For a tool with one parameter, this is insufficient.

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 already provides 100% coverage with a descriptive example for the 'query' parameter. The description adds minimal extra meaning ('any product category') but does not introduce new details or clarify why the parameter is optional (required parameters: 0). Schema does the heavy lifting, so a baseline score of 3 is appropriate.

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 'Stiftung Warentest results', and it qualifies the scope as 'any product category'. This distinguishes it from sibling tools like product_reviews or review_search by specifying the unique source (Stiftung Warentest).

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?

There is no explicit guidance on when to use this tool versus alternatives. Sibling tools like product_reviews and review_search may overlap in functionality, but the description does not mention them or provide exclusion criteria. The phrase 'for any product category' implies a broad use case, but the intended context relative to siblings is missing.

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