add_chart

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

No annotations are provided, so the description carries the full burden. It explains parameter defaults and constraints (e.g., categories_range required for scatter), but it does not disclose side effects (e.g., overwriting content), permissions, or error behavior. The description provides moderate behavioral 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 front-loaded with a clear purpose and then uses paragraphs to explain parameters. It is reasonably concise for the amount of detail, though could be more structured with bullet points for parameter lists.

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 has 11 parameters (3 required) and no output schema, the description covers core usage but omits return value or success/failure indications. It adequately covers parameter dependencies but is not exhaustive.

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 add meaning. It explains chart_type values, data_range and categories_range semantics, position format, and size defaults. However, it does not describe title, x_title, or y_title, which are present in the schema. Overall, it adds significant value beyond the 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 verb 'Embed a chart in a sheet.' It lists supported chart types and explains how data_range, categories_range, and position work. This distinguishes it from sibling tools like delete_chart or list_charts.

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?

While the description explains parameter usage thoroughly, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to embed vs. when to list or delete charts). The usage context is implied but not directly stated.

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