cancel_stop_order

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

While annotations declare destructiveHint=true and readOnlyHint=false, the description adds crucial behavioral context that explicit confirmation (confirm: true) is required to execute the cancellation, indicating a safety-gated destructive operation.

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?

Single sentence structure front-loaded with action, zero redundant content. Parenthetical efficiently conveys critical safety requirement without verbosity.

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?

Adequately complete for destructive operation with 100% schema coverage. References domain context (T-Investments) and safety confirmation. No output schema present to require additional description.

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 100%, establishing baseline 3. Description adds value by emphasizing via 'требуется' that confirm parameter is mandatory (not optional), adding semantic weight beyond the schema's literal description.

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?

Description provides specific verb 'Отменить' (Cancel) with specific resource 'стоп-заявку' (stop order) and domain 'Т-Инвестициях'. Clearly distinguishes from sibling 'cancel_order' by explicit resource qualification.

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?

Mentions critical prerequisite '(требуется confirm: true)', providing implicit safety guidance. However, lacks explicit comparison to sibling 'cancel_order' regarding when to use stop-order cancellation vs regular order cancellation.

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