Similar products

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the scoping sense of "similar" and the cheapest-sort trick, but says nothing about result volume or pagination behavior beyond what the schema states.

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 short sentences with zero filler; the core purpose leads and the two routing hints follow. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. What remains unaddressed is how this tool relates to the overlapping sibling dk_find_cheapest and how paging behaves in practice, leaving a small ambiguity for the agent.

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 baseline is 3, but the description goes beyond the schema by attaching intent to a specific enum value: sort='cheapest' yields cheaper alternatives. That is genuine semantic value the bare "Order of the results" schema text does not convey.

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 and resource ("List products similar to one product") and immediately disambiguates the fuzzy word "similar" as "same kind, other models and brands." It also names the sibling to use instead for comparison (dk_compare), so an agent can place it against alternatives without reading schemas.

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?

Gives actionable routing: use sort='cheapest' for cheaper alternatives, and use dk_compare to compare two or more products. It lacks explicit when-not guidance (e.g., versus dk_search, dk_find_cheapest, or dk_category_products for browsing a category), so the alternative space is only partially mapped.

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