calculate_max_pain

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

No annotations are provided, and the description lacks behavioral details such as data sources, calculation methods, prerequisites (e.g., need options chain data), or side effects. The description is purely definitional.

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?

The description is concise at three sentences, with the first sentence stating the purpose, the second defining the term, and the third providing context. No wasted words, but it could be more structured with a bulleted list.

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?

Without an output schema, the description fails to explain what the tool returns (e.g., a single number, an object with strike price and total OI). This is a significant gap for a calculation 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?

The input schema covers both parameters with descriptions (schema coverage 100%). The description does not add any new information about parameter semantics beyond what the schema already provides.

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 states the tool calculates the max pain price for an options expiration and defines what max pain is. It clearly distinguishes from sibling tools like calculate_greeks or get_options_chain by its specific focus.

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 mentions that many traders believe prices gravitate toward max pain as expiration approaches, implying when to use it (near expiration). However, it does not explicitly say when to use this tool versus alternatives like calculate_greeks or get_options_chain, and provides no exclusions.

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