generate_dual_axes_chart

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation (generating a chart without side effects). The description adds context by explaining what a dual axes chart is and its typical use case (combining bar and line charts for trend and comparison), which helps the agent understand the output behavior. However, it doesn't disclose any additional behavioral traits like performance characteristics, rate limits, or specific error conditions beyond what annotations imply.

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, well-structured sentence that efficiently explains the tool's purpose and provides a concrete example. It's appropriately sized for a chart generation tool, with no redundant information. However, it could be slightly more front-loaded by explicitly stating it's for creating visualizations, though the current structure is still clear and concise.

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 tool's complexity (8 parameters with nested objects) and the absence of an output schema, the description is minimally adequate. It explains what the tool generates but doesn't detail the output format (e.g., image URL, base64 data, chart object). With annotations covering safety (readOnlyHint=true) and a rich input schema, the description meets basic requirements but leaves gaps about the result format, which could be important for an agent to use the tool effectively.

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 100%, meaning all parameters are well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain parameter relationships or provide additional examples). Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to given the comprehensive schema.

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 tool's purpose: 'Generate a dual axes chart which is a combination chart that integrates two different chart types, typically combining a bar chart with a line chart to display both the trend and comparison of data.' It specifies the verb ('generate') and resource ('dual axes chart') with a concrete example ('sales and profit over time'). However, it doesn't explicitly differentiate from sibling tools like 'generate_column_chart' or 'generate_line_chart' beyond mentioning the combination aspect.

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 provides no guidance on when to use this tool versus alternatives. It mentions the chart type ('dual axes chart') and gives an example use case ('trend of sales and profit over time'), but doesn't specify when to choose this over other chart types like 'generate_area_chart' or 'generate_bar_chart', nor does it mention any prerequisites or exclusions for usage.

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