search_products

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

The description discloses that the tool returns a list of matching products with lowest price, number of offers, and page URL, but does not mention any side effects, rate limits, or additional behavioral traits. Since annotations are absent, the description carries the burden but lacks detail like whether it's read-only.

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 4 lines, well-structured, and front-loaded with the purpose. Every sentence adds value: purpose, sort options, price range, and return structure. No redundant or unnecessary text.

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 the complexity (5 params, has output schema, sibling tool), the description covers the main aspects: purpose, key parameters, and return value. It lacks explanation for 'limit', but with the output schema clarifying return fields, it is mostly 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?

Schema description coverage is 0%, so the description must add meaning. It explains 'sort' (relevance/price_asc/price_desc) and 'min_price'/'max_price' (euro range). 'query' is implied by 'search by name or keyword', but 'limit' is not described, leaving some parameter semantics incomplete.

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 searches geizhals.de for products by name or keyword, which is a specific verb and resource. It distinguishes from the sibling tool 'get_product' which likely retrieves a single product's details.

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 provides context on using sort and price range parameters but does not explicitly state when to use this tool versus the sibling 'get_product' or any conditions for not using it. The guidance is implied but not explicit.

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