moex_search

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds non-obvious behavioral context beyond that: the search is fuzzy and results may contain multiple non-trading rows, with an explicit disambiguation rule. It does not mention rate limits or pagination.

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?

Three dense sentences, front-loaded with purpose, then return shape, then the disambiguation rule. Every sentence earns its place, though the return-field list could be trimmed since it is partially derivable from the columns parameter.

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 no output schema, the description correctly compensates by listing the returned columns, and it explains the fuzzy-match semantics. For a 9-parameter tool it leaves some parameter behavior (limit, only_trading, CSV routing) to the schema, but the core contract an agent needs is present.

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 67%, and the description adds real value for the query parameter by enumerating the accepted identifier formats (ticker, name, ISIN, issue number, INN). It also relates to the columns parameter by naming default returned fields, but it says nothing about group, market, limit, or only_trading, leaving part of the surface unexplained.

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 ("Поиск бумаг Мосбиржи") plus the identifier types accepted (ticker, name, ISIN, issue number, issuer INN) and the returned fields. This is clearly a lookup/discovery tool, distinct from moex_quote or moex_candles, though it never names a sibling to sharpen the contrast.

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 gives operational guidance on interpreting fuzzy results ("выбирай строку с is_traded=1 и совпадающим shortname/isin"), which is genuinely useful. However, it never says when to use this tool versus moex_security or moex_quote, so the routing guidance is only implied.

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