post_stop_order

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable safety context that explicit confirmation is required, which helps the agent understand the guarded nature of the operation. Does not elaborate on conditional execution behavior or financial risks.

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?

Extremely efficient single sentence with parenthetical for the critical constraint. No extraneous words, front-loaded action verb, appropriately scoped for a trading API.

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?

Covers the essential safety prerequisite (confirm flag) for a destructive financial operation. However, given the complexity of stop orders (conditional triggers, stop-loss vs take-profit mechanics), the description could benefit from mentioning that this creates a deferred/conditional order rather than immediate execution.

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?

Input schema has 100% description coverage, establishing baseline 3. The description emphasizes the confirm parameter requirement, but does not add semantic detail beyond what the schema already provides for the 10 parameters.

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?

Clearly states the specific action (выставить/place) and resource (стоп-заявку/stop order) and domain (Т-Инвестиции). Distinguishes from sibling 'post_order' by specifying 'stop order' vs presumably regular orders.

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?

Specifies the critical invocation constraint that confirm: true is required for execution. However, lacks explicit guidance on when to choose this tool over 'post_order' (stop orders vs immediate orders) or primer on stop-loss vs take-profit selection.

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