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

Annotations already declare readOnly, idempotent, non-destructive, closed-world operation, so safety is covered. The description adds genuinely new semantics: that 'listed price' is the retailer's own comparison price not verified by the service, that results carry an as-of time, and that made_in_usa is official-source 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?

One dense sentence that front-loads the returned-field list. The closing 'Optional filters including made_in_usa' is redundant with the earlier mention and could be cut, but overall waste is minimal.

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 carries the return-shape burden and does so by enumerating the fields. Zero required parameters keeps invocation simple, and the listed-price caveat removes the main source of misinterpretation; only filter behavior (brand/limit) is left thin.

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 60%, with category, max_price, and made_in_usa documented in the schema but brand and limit undocumented anywhere. The description restates made_in_usa but adds nothing for brand, limit, or filtering syntax, so it only marginally improves on the schema.

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 resource (verified motorcycle gear deals) and enumerates the returned fields, so an agent knows exactly what it retrieves. It does not explicitly name or contrast against siblings like list_fit_guides or size_recommendation, but the domain is distinct enough that confusion is unlikely.

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 statement of when to call this versus alternatives, and no prerequisites or exclusions. The trailing 'Optional filters including made_in_usa' repeats the field already named and gives no trigger conditions for using filters.

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