createFMartBot

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

With no annotations, the description carries full burden. It discloses rate limits (10 req/s), compliance/KYC checks, and explains bot behavior including the meaning of parameters like martingale_mode and auto_cycle_toggle. It also notes the need for the bot_id for subsequent calls.

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?

The description is fairly long but well-structured into paragraphs covering behavior, parameters, preconditions, and hints. Some redundancy (e.g., mentioning getFMartLimit twice) could be trimmed, but it remains clear.

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?

Given 17 parameters, no output schema, and no annotations, the description covers the core bot logic and parameter meanings well. However, it lacks details on error responses, exact return structure, or edge cases, leaving some gaps for a complex create endpoint.

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 add meaning. It explains the key parameters (symbol, mode, leverage, price_float_percent, etc.) and interprets enums (e.g., martingale_mode: 1=Long, 2=Short; auto_cycle_toggle=1 for restart). This compensates for the schema's lack of descriptions.

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?

The description clearly states that the tool creates a futures Martingale trading bot and explains the bot's behavior (opens position, adds on dips/rises). It distinguishes itself from sibling tools like closeFMartBot and getFMartDetail by focusing on creation.

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 explicitly tells the agent to call getFMartLimit first to validate parameters, providing clear when-to-use guidance. It does not explicitly exclude alternative creation tools, but the context is specific enough.

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