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

No annotations are provided, so the description must carry the behavioral disclosure burden. It discloses the return dictionary including an 'error?' key, hinting at failure handling, but it does not state side effects, behavior on missing/invalid files, or assumptions about the JSON structure.

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 front-loaded purpose line followed by a compact return-type listing. There is no filler, and every element adds useful information about what the tool does or returns.

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 return dictionary provides a good map of outputs, but the two parameters remain effectively undocumented and error-handling detail is minimal. For a simple parser this is close to adequate, but explicitly defining 'top_n' and the expected location of 'file_path' would make it complete.

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 description coverage is 0%, and the description never mentions 'file_path' or 'top_n'. 'top_n' can be inferred from 'top_trades_md', but the description does not compensate for the schema's silence regarding path format or the meaning/limits of 'top_n'.

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 names a specific action and resource: 'Parse Freqtrade backtest-result JSON → markdown digest.' It also lists the exact return keys, making the tool's function concrete and clearly distinct from its unrelated siblings.

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?

When to use the tool is implied by the input type ('Freqtrade backtest-result JSON'), but there is no explicit when/when-not guidance or mention of alternatives. Since all sibling tools are unrelated, there is no direct selection ambiguity, but the guidance is still implicit rather than stated.

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