moex_trades

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds nothing behavioral beyond that — no rate limits, no delay/data-freshness caveats for a live tape, no note on empty-session behavior. "newest first" is a return-ordering detail, not behavioral transparency.

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?

Two short sentences, purpose front-loaded, no filler. It is terse rather than padded, though the brevity also reflects under-specification.

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?

For an 8-parameter tool with no output schema and only 50% parameter documentation, the description is thin: it does not explain how the table/CSV split behaves, what board means, or what an empty current session returns. Adequate minimum but with clear gaps.

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 ~50%. The description supplies the semantics for latest ("N последних, новые первыми"), which the schema leaves undocumented, but board, secid and max_rows remain unexplained in both places. Baseline 3 is appropriate given partial schema coverage plus one genuinely useful parameter clarification.

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?

"Сделки текущей сессии" names a specific resource (trades) with a scope qualifier (current session), which implicitly contrasts with moex_history/moex_history_by_date. However it never names a sibling tool to route the agent explicitly.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as moex_candles or moex_history. The agent must infer that this is for intraday/current-session tape rather than historical data.

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