Load deterministic demo chart

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

The annotations already declare destructiveHint=false and readOnlyHint=false. The description adds that the data is 'deterministic synthetic OHLCV', which clarifies it's a safe demo/reset function. However, the word 'reset' could imply destructive behavior, but it's consistent with the non-destructive demo purpose. No additional behavioral details like what gets cleared or what happens to existing data are disclosed.

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 sentence that directly states the action and purpose. It is concise and contains no fluff, earning full marks for efficiency.

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?

Despite having 4 parameters and no output schema, the description provides minimal context. It does not explain return values, the relationship between parameters and the generated data, or how this tool interacts with the chart state. For a testing/onboarding tool, the lack of parameter and behavior details makes it incomplete.

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?

With 0% schema description coverage, the description was expected to compensate by explaining what seed, count, symbol, and interval do. It does not mention any parameters at all, leaving the agent with no understanding of how these affect the synthetic data generation. This is a critical gap.

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 uses specific verbs 'Reset' and 'load' with a clear resource ('the chart' and 'deterministic synthetic OHLCV'), indicating it loads demo data. This clearly distinguishes it from sibling tools like chart_import_csv (import real data) and chart_set_data (set specific data). The purpose is immediately clear.

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 phrase 'for testing and onboarding' provides some context for when to use this tool, but it does not explicitly state when not to use it or mention alternatives. No exclusions or comparisons to other chart_* tools are provided, leaving the agent to infer usage boundaries.

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