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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is narrower. It adds real context: the two accepted input shapes (TradingView 'List of trades' CSV vs JSON trade list), that commission settings are applied during recomputation, and that output is a per-metric MATCH/MISMATCH verdict. It does not say what happens if no input is supplied, but nothing contradicts the annotations.

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?

A single dense sentence with the action and inputs front-loaded and the output contract at the end. Every clause carries information, though it reads as a run-on that could be split for scanning.

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?

With no output schema, the description correctly states the return shape (per-metric MATCH/MISMATCH), which is what an agent most needs. The remaining omission is the meaning/role of initial_capital and the expected structure of the trades array, both of which are left to inference.

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 60% and the description partially compensates: it clarifies that drawdown is closed-trade only, that commission settings affect the math, and that trades_csv is specifically the TradingView Strategy Tester export. However, initial_capital is never mentioned and the trades array items are untyped, so gaps remain.

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+resource: recompute four named metrics (net profit, win rate, profit factor, closed-trade drawdown) from a TradingView CSV or JSON trade list, then label each claimed metric MATCH/MISMATCH. The sibling set (pine_lint, pine_integrity, kr_*) is in unrelated domains, so no differentiation is needed.

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 reconciliation framing implies the use case (verifying claimed backtest metrics against raw trades), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. Guidance is inferable rather than stated.

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