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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: fuzzy/typo-tolerant matching and the fact that only in-stock, new-condition items count toward the price filter. Since there is no output schema, its statement of the returned fields (names, slugs, lowest new prices) is also valuable.

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?

Two dense sentences with no filler; the searchable facets are front-loaded and the return-value note is appended where it belongs. Every clause earns its place.

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, the description correctly compensates by naming the returned fields, and the annotations carry the safety profile. Facet and price-filter semantics are covered; only result ordering/pagination for the limit parameter is left implicit, which is a minor gap for a read-only search.

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 coverage is 80% and the schema already documents brand, query, category and maxPriceUsd. The description adds the typo-tolerance behavior of the query parameter and restates the in-stock constraint of maxPriceUsd, which the schema mentions but does not fully explain. The limit parameter's semantics remain undocumented in both places, keeping this short of a 5.

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?

States a specific verb (search) and resource (guitar and bass pedals) plus the searchable facets (brand, model, nickname, type). It is clearly distinct from the singular get_pedal and the pairwise compare_pedals siblings.

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?

It notes the price filter is optional and that matching is typo-tolerant, which implicitly tells the agent this is the broad discovery entry point. However, it never names when to prefer get_pedal or compare_pedals, so the routing decision is left to inference.

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