pulse_max_pain_events

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

No annotations provided, so description carries full burden. Discloses that it returns positions, entry/MAE/exit prices, realized PnL, max drawdown %. Implicitly read-only with no side effects. Lacks details on data source or time range but adequate.

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?

Three sentences front-loaded with core purpose, then output specifics and filter criteria. No redundant words. Ideal length and structure.

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 lists expected fields. Covers filtering (minPnl, drawdown). Does not specify time range or exchange, but sufficient for a data query tool. Minor gaps prevent 5.

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 provides 100% descriptions for all 5 parameters. Description adds general context ('material positions', 'bounded drawdowns') but does not significantly extend schema meaning. Baseline 3 applies.

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 uses specific verb 'Find' and clearly identifies resource as 'biggest survived drawdowns' with explicit criteria (closed perp positions, high MAE, still profitable). Distinct from sibling tools like pulse_anti_survivors and pulse_backstop_events.

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 purpose clearly: find diamond hands winners. Lists output and filters (minPnl, bounded drawdowns). Does not explicitly exclude use cases or name alternatives, but context makes it clear.

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