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

No annotations are provided, so the description carries the full burden. It does disclose the output semantics (a series of percentage declines measured from the running peak), which is more than the schema offers, but it omits the input encoding (the parameter is typed as string while the description says "array"), whether values are fractions or percents, and any error behavior.

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 compact sentences, with the definition of drawdown front-loaded before the input instruction. The leading "Drawdown:" label duplicates the tool name and is the only wasted token.

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 single-parameter math utility with no annotations and no output schema, the description covers the core computation and roughly what the result represents. It is still incomplete on input format ambiguity (string vs array), the numeric convention of the output, and how it relates to the max-drawdown sibling.

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%, but the schema's own text ("Values to process") is uninformative, and the description only adds that the values should be supplied as an array. It does not reconcile the string type in the schema with the "array" phrasing, nor specify ordering, numeric format, or whether a price series is required rather than returns.

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?

States a specific verb (calculate) and resource (drawdown series of an asset's price) and defines the concept precisely as the percentage decline from its running peak. It does not distinguish itself from the closely related sibling x402-max-drawdown, so the agent cannot be certain which of the two to pick from the text alone.

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?

"Provide values array" is an input instruction, not usage guidance. There is no statement of when to use this versus the sibling x402-max-drawdown (single worst drawdown) or x402-rollowing/cumulative tools, and no prerequisites or context for the kind of input expected.

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