tv_chart_data_export

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

Annotations already set destructiveHint=true. The description adds context: 'triggers a browser download' and 'Saves the download to ./exports', which goes beyond the annotation by detailing the side effect and target location.

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?

Two short sentences with no wasted words. The first sentence states the core action, the second adds critical context (destructive behavior). Front-loaded and efficient.

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?

Given the simplicity (no params, no output schema), the description covers the key aspects: what it does, where it saves, and its destructive nature. Missing details like file naming or return confirmation, but overall adequate.

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?

The tool has zero parameters; the schema coverage is 100% (no params). The description implicitly states it uses the current state ('Export the current chart data'), which meets the baseline for no-parameter tools.

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 clearly states the verb 'export' and the resource 'current chart data to CSV', with a specific destination './exports'. It is distinct from sibling tools like tv_screenshot or tv_read_chart.

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 description emphasizes the destructive nature ('DESTRUCTIVE: triggers a browser download') but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like tv_screenshot for visual output or tv_read_chart for textual data.

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