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

Annotations only declare readOnlyHint=true, so the description carries the rest of the burden. It discloses the non-obvious measurement semantics (ADD measured entry-to-exit, DROP as foregone return exit-to-latest-close, both vs S&P over the same window), which materially affects interpretation. It omits any statement about data freshness/latency or weighting assumptions, keeping it short of a 5.

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?

Front-loads the one-line purpose before the methodology and routing note, and each sentence serves a distinct purpose. However, the verbose restatement of the return shape duplicates the existing output schema and could be trimmed.

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?

Read-only annotations plus a full output schema mean the safety and return-value burdens are covered elsewhere. The description adds the computational definitions needed to interpret the numbers correctly, though freshness/coverage caveats for the latest close are unstated.

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% and the enum already enumerates the five valid values, so the schema does the heavy lifting. The description adds only the scoping emphasis "ONE strategy book" and does not explain why pooled behaves differently beyond what the enum description states; baseline 3 is appropriate.

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 artifact (per-trade swap ledger of adds/drops), the benchmark (S&P 500), and the scope (ONE strategy book). It also explicitly routes the agent elsewhere for the book-level time series, so it is distinguishable from siblings like get_strategy_track_record without reading either schema.

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?

Gives the exact question this tool answers ("were the individual trades good?") and names the alternative tool plus the condition that selects it (book-level return series -> get_strategy_track_record). When-to-use and when-to-use-something-else are both explicit.

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