moex_quote

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the ~15-min delay (and the exception for indices), plus the distinct field sets returned for stocks versus bonds. It does not discuss rate limits or error behavior.

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?

Front-loaded with the core purpose and delay caveat, then a compact enumeration of returned fields. The field lists are dense but earn their place by telling the agent what comes back in the absence of an output schema. No filler sentences.

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 carries the burden of describing returns, and it does so for both stocks and bonds, plus the delay caveat. It lacks guidance on choosing among sibling tools, which is the main remaining gap for a tool with 14 siblings.

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 100%, so every parameter is already documented in the schema. The description adds no syntax or format detail about secids, board, columns or the CSV-save options, so the baseline 3 is appropriate.

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: current quotes for one or more securities, and the fact that stocks, bonds and indices can be mixed. It does not explicitly differentiate itself from close siblings like moex_market_snapshot or moex_security, so it falls short of a 5.

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?

The description implies when the tool is relevant (live-ish quotes) and discloses the ~15-minute delay, which shapes expectation. However it never names an alternative or a condition that routes the agent to moex_security, moex_market_snapshot or moex_candles instead.

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