sheets_create_chart

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description does not contradict these. The description adds context about range quoting and overlayPosition structure, but does not disclose side effects, permissions, or return value behavior, which with annotations present leaves the safety profile adequately covered.

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 only three sentences, front-loaded with the core purpose, and every sentence adds meaningful guidance. It is appropriately sized for the tool's complexity.

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 (13 parameters, nested objects), the description focuses on the most error-prone aspects. While it does not explain all options like axes or legends, the schema descriptions cover those. The absence of an output schema is mitigated by the clear annotation hints.

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 baseline is 3. The description adds value beyond the schema by centralizing the quoting rule for sheet names with spaces and clarifying the nested overlayPosition structure with anchorCell fields, which helps avoid common mistakes.

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 'Create a chart in a Google Sheets spreadsheet' with a specific verb and resource. It does not explicitly distinguish from sibling tools like sheets_update_chart or sheets_delete_chart, but the verb 'create' makes the primary purpose clear.

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 implies usage for creating charts but does not provide explicit when-to-use versus alternatives such as updating or deleting charts. It includes useful tips about quoting sheet names and using overlayPosition, but these are more parameter handling than usage guidance.

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