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

With no annotations, the description carries the behavioral burden and does substantial work: it discloses the 20-result cap, the absence of full catalog enumeration, the presence of canonicalUrl per hit, and the optional image blocks with display instructions. It does not cover error cases or other returned fields, but it gives meaningful operational behavior beyond the schema.

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 compact and front-loaded with the core search scope, then the result limit, then the output/display requirements. Every clause carries information, though the display instructions are dense and could be slightly tightened.

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?

For a search tool with no output schema and no annotations, the description explains the search scope, result cap, and key output behaviors (canonicalUrl, images). However, it does not describe other likely result fields (e.g., product name, price, availability), which would help an agent present results fully; pagination and error behavior are also absent.

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 the schema already explains query as free text (instrument, brand, model, English allowed) and limit with default/max. The description adds no new parameter-level meaning; it only restates the 20-result cap, which aligns with the limit 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 states a specific action ('Sucht') and a concrete resource ('GEWA-Instrumenten- und Zubehörsortiment von musikalienhandel.de'), making the tool's scope clear. It also notes the result is a limited hit list, but it does not explicitly contrast itself with sibling tools like search_sheet_music or search_bargain_stock.

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 intended use is implied by the resource scope: search the GEWA instrument/accessory catalog. The 'keine vollständige Katalog-Enumeration' note gives an exclusion, but there is no explicit guidance on when to prefer this tool over siblings or when not to use it.

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