flatten_positions

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

No annotations provided. Description reveals default dry_run=true and that market orders are used, but does not disclose potential side effects like slippage or market 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?

Two sentences, front-loaded with purpose, no redundant 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?

For a simple 2-param tool with no output schema, description covers purpose, filtering, and default. Could mention confirmation behavior, but adequate.

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?

Description adds 'optionally filtered by symbol' and 'Default dry_run=true' beyond schema. Schema already describes symbol well, but dry_run semantics are minimally covered.

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?

Description clearly states 'Close every open position with opposite-side market orders, optionally filtered by symbol.' This is a specific verb-resource combination that distinguishes from siblings like cancel_all or cancel_order.

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?

Explicitly says 'Use for close everything operator actions or end-of-day flatten.' Provides context, though does not explicitly exclude other scenarios or compare with alternatives.

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