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

The description adds important behavioral info beyond annotations: it will advance to fill orders and hold without new orders until completion or max_bars. It also notes it does not select a strategy, which is useful context.

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?

Two sentences, no waste. First sentence describes core behavior, second clarifies it is execution-only. Efficient and front-loaded.

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, the description adequately covers the tool's lifecycle (create orders, advance, hold). Missing explicit mention of return value or blocking behavior, but the behavioral description compensates.

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%, so baseline is 3. The description does not add significant meaning beyond the schema; it mentions max_bars in context but the schema already describes it. The rationale parameter is briefly mentioned as copied onto orders.

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 the tool creates sell/cover orders to flatten all positions, then advances to fill them. It distinguishes from siblings by specifying it executes an exit decision and does not select a strategy.

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 implies use after an exit decision, but does not explicitly state when not to use or name alternative tools. The context is clear enough given sibling tool names, but explicit exclusions would improve clarity.

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