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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds concrete behavioral details: returns a limited result list (max 20) and each hit contains a canonicalUrl field that should be displayed with specific product mentions. It does not mention sorting, pagination, or error cases, but for a simple search tool this is meaningful coverage.

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: two sentences, with the search scope front-loaded, followed by the result cap and the canonicalUrl display instruction. Every sentence adds useful operational information without redundancy.

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 simple search tool with two well-documented parameters and no output schema, the description adequately covers the key context: what is searched, the result cap, and the expected URL field. It could be more complete by describing additional result fields or typical search behavior, but it is sufficient for a basic tool.

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%: both query and limit are already described in the input schema. The description does not add much parameter-level meaning beyond noting the 20-item cap, which matches the schema. Baseline 3 applies because the schema already handles parameter documentation.

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 a specific verb ('Sucht') and resource ('Bestand an B-Ware, Vorführ- und gebrauchten Instrumenten (Katalog 29) von musikalienhandel.de'). It distinguishes this tool from siblings like search_instruments and search_sheet_music by emphasizing the discount/used-instrument catalog scope.

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 a clear context: this is for searching B-ware, demo, and used instruments from catalog 29, calling it a 'central USP'. However, it does not explicitly state when to prefer this tool over alternatives such as search_instruments, nor does it name exclusions. Usage is implied rather than explicitly guided.

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