Yandex Market: get prices

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

With no annotations present, the description does valuable work by stating that the operation is read-only, never changes prices, and that money values are decimal strings. However, it does not disclose pagination behavior via the cursor, the meaning of the limit, or how business_id/connection_id resolution behaves at runtime, so the behavioral picture is incomplete.

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 short and front-loaded with the core return values. 'Read-only' and 'never changes prices' are slightly redundant, so it is not perfectly tight, but every sentence otherwise contributes useful information without padding.

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?

The output schema presumably covers the return shape, so details about response fields are less critical. However, the description omits important operational context: how cursor pagination works, what limit controls, and when business_id/connection_id are required. An agent could call the tool, but it would have to discover pagination and connection semantics elsewhere.

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 only 50%, leaving limit and cursor undocumented, and the tool description adds no parameter-level meaning whatsoever. The description does not mention pagination, paging size, or the fallback resolution of business_id, so the agent gets no help beyond the already-present schema comments.

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 opens with a specific verb ('Returns'), names the resource ('Yandex Market prices'), and enumerates the returned values (base price, customer price, currency). The explicit 'Yandex Market' scope clearly distinguishes it from sibling price tools for other marketplaces, and 'Read-only' reinforces that it is a retrieval operation.

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 guidance on when to use this tool versus alternatives such as ym_stocks_get, ym_orders_list, or the other marketplace price tools. It also does not mention prerequisites like when business_id must be manually provided or how connection_id should be chosen, leaving selection and setup entirely to inference.

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