generate_column_chart

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

Annotations provide readOnlyHint=true, indicating this is a safe operation. The description doesn't contradict this. It adds some behavioral context about visual perception ('our eyes are better at judging height'), but doesn't disclose important operational details like what format the output takes (image URL, base64, chart object), performance characteristics, or any limitations. With annotations covering safety, the description adds minimal but not misleading context.

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 run-on sentence that mixes purpose statements with visual perception theory. It's not well-structured or front-loaded with essential information. While not excessively long, it's not efficiently organized, with the visual perception explanation not clearly earning its place for tool selection purposes.

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?

For a complex visualization tool with 10 parameters, nested objects, and no output schema, the description is inadequate. It doesn't explain what the tool returns (critical for a chart generation tool), doesn't provide examples of typical use cases, and doesn't address common pitfalls. With rich schema but no output schema, the description should compensate more than it does.

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%, so the schema already documents all 10 parameters thoroughly. The description provides no additional parameter information beyond what's in the schema. It doesn't explain the relationship between parameters or provide usage examples. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 states 'Generate a column chart' which is tautological with the tool name. It provides some context about when column charts are best used (comparing categorical data, values close), but doesn't clearly articulate what the tool actually produces (e.g., an image, chart object, visualization). The purpose is vague beyond restating the name.

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 mentions that column charts are 'best for comparing categorical data' and 'when values are close', which provides some general chart selection guidance. However, it doesn't explicitly state when to use this tool versus its many siblings (e.g., bar_chart, line_chart, pie_chart) or provide clear alternatives. No explicit when-not-to-use guidance is provided.

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