closeComboBot

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

Discloses key behaviors: cancels orders, closes positions, requires running state, includes rate limit. With no annotations, this covers most behavioral traits needed for an agent to assess impact.

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?

Concise; three brief paragraphs front-load the main purpose and provide additional details without redundancy. Every sentence adds value.

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?

Good completeness for a mutation tool with no output schema and no annotations. Covers behavior, prerequisites, post-action, and rate limit. Lacks explicit return value description, but partly mitigated by post-action hint.

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 has 0% coverage, so description must compensate. It explains bot_id source but only vaguely describes stop_type as 'indicates the reason' without explaining enum meanings (0-15). This leaves ambiguity for a critical parameter.

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 it closes a running futures combo trading bot by canceling orders and closing positions. Does not explicitly differentiate from sibling tools like closeGridBot, but the name and context sufficiently target combo bots.

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 when-to-use guidance: only running bots can be closed. Includes a direct agent hint explaining how to obtain bot_id and suggests checking getComboDetail afterward. Also mentions rate limit.

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