setTradingStop

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

With no annotations, description carries full burden. Discloses mode behavior, equal size constraint, cancellation method, and positionIdx meaning. Missing side effects (immediate? reversible?), permission requirements, or error handling. Adequate but not comprehensive.

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?

Four sentences efficiently convey purpose and key rules. Starts with general purpose, then agent hint with parameters. Could be slightly better structured (e.g., separate parameter descriptions), but no wasted words.

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?

Despite complexity (16 params, no output schema, no annotations), description covers only a fraction of parameter semantics and lacks expected behavior, output, and error conditions. Many required fields (category, symbol) are not explained. Significant gaps remain.

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 0%, so description must compensate. Adds meaning for tpslMode (Full/Partial), tpSize/slSize equality, cancellation via '0', positionIdx values. However, 12 other parameters (category, symbol, takeProfit, etc.) are undocumented, leaving significant gaps.

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 tool configures trading stop parameters (TP, SL, trailing stop) on open positions. Uses specific verb 'configure' and resource 'trading stop parameters'. Distinguishes itself from sibling order tools by focusing solely on stop settings.

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?

Provides explicit agent hint on usage: use for setting TP/SL/trailing stop, explains Full vs Partial mode, requirement for equal sizes in Partial, cancellation via '0', and required positionIdx. Lacks explicit when-not-to-use or alternatives, but context is clear.

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