sheets_add_chart

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

With no annotations, the description carries the full burden. It discloses the allowed chart types, which is helpful, but it does not mention any side effects, whether the operation is additive/destructive, or whether it requires an existing sheet/chart. This is a minimal behavioral disclosure.

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 extremely concise and front-loaded with the purpose ('Add a chart') followed by the relevant types list. Every sentence serves a purpose, with no wasted words.

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?

Despite having an output schema, the description is incomplete for a 5-parameter tool with zero schema descriptions. It does not clarify how to specify data_range or which sheet is targeted, and it lacks guidance on prerequisites or constraints beyond the chart type list.

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 the description must explain parameter semantics, but it only addresses the chart_type parameter via the types list. It provides no elaboration on spreadsheet_id, sheet_id, data_range, or title, leaving the agent to infer from parameter names.

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 uses a specific verb ('Add') with a clear resource ('a chart') and lists supported chart types, which distinguishes it from sibling tools like sheets_add_sheet or sheets_add_conditional_format. However, it does not explicitly state the target spreadsheet context, though the tool name clarifies that.

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 is provided about when to use this tool over alternatives, prerequisites, or what to do before adding a chart (e.g., whether data_range must be formatted a certain way). The description gives no context for selection.

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