pulse_perfect_exits

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

Discloses output fields and filtering criteria (minPnl, minCapturePct). No annotations present, so description carries full burden. Could mention default format (useToonFormat) but still provides good behavioral insight.

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?

Very concise: 4 sentences, front-loaded with purpose. No 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?

No output schema, but description explains return fields. Covers main functionality and filtering. Lacks mention of useToonFormat parameter effect on output, but overall sufficient for a paginated list tool.

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. Description adds minimal context beyond schema (e.g., 'material positions' for minPnl, 'capped at 100' for MFE capture). Not significantly enhancing schema 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 the tool finds perp positions that exited near the top based on MFE capture percentage. It uses specific verbs like 'Find' and 'Returns', and distinguishes from siblings by focusing on well-timed exits.

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?

No guidance on when to use this tool over related sibling tools (e.g., pulse_recent_closed_positions, pulse_trader_closed_positions). Does not provide context for alternatives or exclusions.

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