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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely useful context: data is derived from stats artifacts and the response includes a Vega-Lite spec. It does not disclose that the 'limit' cap of 5000 will truncate the series or how truncation is signaled, which matters for a data-extraction tool.

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 that front-loads the verb and resource, then names the output artifacts. No filler and nothing redundant.

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 does the important work of naming the return contents (points plus Vega-Lite spec), which is the key completeness item for this tool. However, for a tool with three undocumented parameters and a hard limit cap, the absence of any note on truncation or backtestId semantics leaves a real gap.

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%, so the description must carry parameter meaning itself. It does list the four series values, which reinforces the enum, but leaves 'backtestId' (the required parameter, uuid format, presumably which backtest artifact to read) and 'limit' (default 1000, max 5000, truncation behavior) entirely unexplained.

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?

Names a specific verb ('Builds') and resource ('chart-ready time series data') and enumerates the four series types (equity/portfolio/drawdown/returns) along with the source ('stats artifacts') and the output shape ('points + Vega-Lite spec'). An agent knows exactly what it gets back, though it does not name the sibling it differs from (e.g. get_backtest_visuals or get_portfolio_series).

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?

There is no when-to-use or when-not-to-use guidance. With nearby siblings like get_backtest_visuals, get_portfolio_series, and live_chart, the agent gets no signal about when this chart-series tool is the right choice versus those alternatives.

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