execute_trade

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

No annotations provided. Description clearly states override behavior, immediate execution, and post-entry management. Does not contradict any structured data, but could mention safety or permission considerations.

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?

Compact and well-structured: opens with purpose, explains override behavior, provides practical examples. Every sentence adds value without redundancy.

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 no output schema and 5 parameters, description covers entry behavior and post-strategy management. Lacks details on error handling or return format, but sufficient for typical agent usage.

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?

Adds significant value beyond schema descriptions: explains optional nature of stake_amount and price, illustrates parameter usage with natural language examples, clarifies order_type defaults. Schema coverage is 100% but description enhances understanding.

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?

Describes a specific action (force-enter trade) with clear verb-resource pairing, distinguishes from normal strategy-driven trades and sibling 'force_exit_trade'. Natural language examples reinforce purpose.

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?

States when to use (bypass strategy, force entry) and notes position will be managed afterward. Indirectly excludes normal trading workflow, but lacks explicit when-not-to-use or alternative tools.

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