create_chart_from_spec

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

No annotations provided, so description must fully disclose behavior. It states 'Create' but does not mention what the tool returns, whether it modifies the spreadsheet immediately, or any side effects (e.g., overwriting existing charts). Missing critical behavioral details for a creation tool.

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 sentences: first defines purpose, second gives usage guidance. No extraneous words, efficient and front-loaded.

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 no output schema, no annotations, and 8 parameters with 0% schema coverage, the description is incomplete. It lacks parameter details, return value, and behavioral context beyond basic purpose.

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 0%, so description must compensate. It mentions 'chart_spec' as a full API object but does not explain other parameters like 'sheet', 'anchor_cell', dimensions, or offsets. Parameter names are somewhat self-explanatory, but lacking explicit context for an AI.

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 clearly states verb 'create' and resource 'embedded chart from a full Sheets API ChartSpec object'. It distinguishes from sibling tool 'create_chart' by specifying it's for complex chart types not covered there.

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?

Explicitly states when to use: 'Use this for histogram, scorecard, bubble, candlestick, waterfall, treemap, org, or other chart specs not covered by create_chart'. This implicitly tells when not to use, but lacks prerequisites or explicit exclusions.

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