Карточка товара Megamarket

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

There are no annotations, so the description carries the burden. It clarifies the return content (gallery, price, characteristics, description) but does not explicitly state that it is a read-only operation or disclose error/rate-limit behavior. The verb 'returns' implies a safe read, but more context would improve transparency.

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?

A single sentence with no wasted words; the core verb, target resource, and key parameter context are all present up front.

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 one parameter, an existing output schema, and simple read semantics, the description covers the necessary context: what is returned, how to obtain the id, and the scope (Megamarket). No further information is critically needed.

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?

The schema already provides a description for the id parameter (identifier from search_products output). The tool description merely repeats this provenance ('по его id из выдачи') without adding new details, so it does not surpass the schema baseline.

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 uses the verb 'Возвращает' (returns) and specifies a detailed product card with gallery, price, characteristics, and description, keyed by product id from search results. This clearly distinguishes it from sibling tools like search_products that return lists.

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 states that the id comes from search_products output, implying this tool is used after a search to fetch details. However, it does not explicitly mention alternative tools or exclusion criteria, only that the id originates from search results.

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