Поиск товаров Megamarket (виджет)

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

No annotations are provided, so the description carries the full burden. It discloses the main behavior (searches and renders a widget), but does not mention side effects, permissions, or rate limits. Since this is a read-only style widget tool, the lack of such details is a minor gap.

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 two sentences, front-loaded with the core purpose and followed by a clear usage condition. Every sentence serves a purpose, and there is no fluff.

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 an output schema present, the return format is already specified. The description provides purpose and usage guidelines, and the 'only when widget requested' clause sufficiently distinguishes it from siblings. Minor omission: no explicit mention of alternative tools, but the guideline implies it.

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 only 50%, and the description adds no parameter semantics beyond what the schema provides. The 'query' parameter is described in the schema, but 'filters' and its nested properties are undocumented, and the description doesn't mention them at all.

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 it searches the Megamarket catalog and renders an interactive widget grid with photo, name, price, and rating. The specific verb 'searches and renders' and the underlined 'widget' distinguishes it from sibling search tools.

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?

Explicitly states 'Использовать ТОЛЬКО когда пользователь явно попросил показать виджет, карточки, интерактивную выдачу или UI', giving a strong condition for when to invoke. This differentiates it from plain search tools and instructs the agent not to read the skill manual.

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