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

With no annotations, the description carries the behavioral burden. It discloses important output/display behaviors: every hit has a canonicalUrl that must be shown directly, and images arrive as marked content blocks that should always be displayed. While it doesn't discuss side effects or rate limits, the purpose of the tool strongly implies a read-only search and the behavioral details present are substantial.

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 front-loaded with purpose and contains important display norms, but a few elements are padding, such as 'Zentraler USP-Case' and 'wichtig ist ein Kaufanreiz'. The text is not overly long, yet it does not earn all its words.

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?

Though there is no output schema, the description covers the critical output/display details for correctly using results, and it explains the core search scenario. It omits no-result handling and sorting, but for two parameters and a straightforward query tool, the description supports practical use well enough.

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 schema has 100% coverage. The description repeats that the query can be a title, composer, or instrument, but it adds no new meaning about the limit parameter or query formatting. Baseline 3 is appropriate because the schema already documents both parameters.

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 uses a specific verb ('Prüft') and names the resource: it checks for B-Ware, reduced, or used alternatives to a queried title, composer, or instrument. It focuses on the alternative-offer use case and distinguishes its intent from siblings, though it does not explicitly name those siblings. It is clear enough for an agent to understand what the tool is for.

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 when-to-use or when-not-to-use guidance. The phrase 'Zentraler USP-Case' suggests importance but does not explain how to choose this tool over sibling tools like search_bargain_stock or search_sheet_music. No exclusions, alternatives, or context are provided.

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