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

No annotations are present, so the description carries the transparency burden. It does disclose that the tool returns the last price, covers specific instruments, uses MOEX ISS, and costs $0.008 USDC. However, it does not mention delays, response shape, pagination, or any operational limitations beyond these basics.

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 compact and front-loaded with the core purpose, followed by concrete examples and pricing. It is appropriately sized with no filler, though the dense parenthetical list could be slightly better structured for readability.

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?

Given the generic schema, no output schema, and no annotations, the description leaves critical gaps: how to form a request, what the response looks like, and how symbols map to asset classes. It is adequate as a high-level summary but not complete enough for an agent to call the tool correctly without further inference.

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 input schema is a generic wrapper with args and extra objects and 0% description coverage, so the description must explain parameters. It provides example tickers and asset types, which hints at possible values, but it does not specify the actual parameter keys, formats, or how to select a currency pair versus an index. This is insufficient for reliable invocation.

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 identifies the tool as providing Moscow Exchange (MOEX ISS) quotes, listing specific asset classes: stocks, currency pairs, and indices. It includes concrete examples (SBER, GAZP, USD/EUR/CNY, IMOEX) that help disambiguate from siblings like cbr_rates, though it lacks an explicit verb such as 'get' or 'fetch'.

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 explicit guidance on when to use this tool versus alternatives such as cbr_rates or ru_search. The description implies usage for MOEX quotes but does not state exclusions, fallback conditions, or how it relates to sibling tools.

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