calculate_max_drawdown

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

The tool appears to be a pure calculation with no side effects, but the description does not disclose output format, edge cases, or assumptions about input ordering. Without annotations, more detail about behavior would be helpful.

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 a single, concise sentence with no superfluous words. It directly conveys the tool's purpose.

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?

The description is adequate for a simple calculation, but it does not explain the expected output (e.g., number, ratio, percentage) or any relevant calculation conventions. Since the tool appears to be part of a larger finance toolkit, additional context would improve completeness.

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 schema provides the parameter type and required status, and the description mentions prices, but it does not explain ordering, time series requirements, or whether values should be adjusted. Basic semantics are implied but not explicit.

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 the operation: calculate maximum drawdown from prices. It is specific enough to distinguish from sibling tools like calculate_returns and calculate_volatility.

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 is given about when to use this tool versus alternatives, nor any conditions or prerequisites. The description only states what it does, not when it should be chosen.

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