export_visualization

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

No annotations provided; description carries full burden. It fails to disclose side effects like file overwriting, permissions, storage location, or error handling. Only states it saves to a file, but no details on return values or behavior, despite output schema existence.

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?

Single sentence of 9 words, no fluff. Action is front-loaded. Every word serves a purpose.

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 existence of output schema (covers return values) and full parameter descriptions, the minimal description is adequate for a simple file save. However, lacks behavioral details that might be needed for robust usage, such as overwrite behavior or error messages.

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%. Description adds value by clarifying 'Plotly figure dict from create_chart()' for figure, specifying format values as 'html' or 'json', and noting filename is 'without extension'. This goes beyond schema descriptions.

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?

Description explicitly states 'Save a chart from create_chart() to a file', specifying the action (save), source (create_chart()), and output (file). This clearly distinguishes from sibling tools like export_data (data export) and export_chart_pdf (PDF specific).

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?

No guidance on when to use this tool vs alternatives such as export_chart_pdf or export_to_datawrapper. Does not mention prerequisites, when not to use, or context for selection among many export-related siblings.

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