add_chart

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

No annotations are present, so the description carries the full burden. It discloses side effects and constraints: literal data caches and embedded workbook, size and position defaults, color defaults, refusals for unsupported chart types/data shapes, backup rotation behavior, atomic save, and refusal to operate on documents open in Word. This is unusually thorough.

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 definition is long but front-loads the core purpose and packs defaults and constraints into dense sentences with no filler. A little restructuring into explicit parameter bullets would improve scannability, but every sentence adds value.

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 13-parameter tool with no annotations, the description covers the key decision points: chart type support, data schemas, placement, sizing, colors, backup, and open-document refusal. The output schema presumably handles return values. The only notable gap is the file_path parameter's role as the target document versus data file paths.

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 descriptions are 0% covered, and the description compensates by defining chart_type values, three data shapes, width/height override semantics, position mutual-exclusion, color count, and backup flag behavior. It does not define title, legend, alignment, or explicitly clarify that the required file_path is the target document, so a couple of parameters still rely on their 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 opens with a specific verb and resource: inserting a native, theme-following Word chart built from data, and explicitly contrasts it with image rendering. The chart type list and data format details make the operation unmistakable and distinguish it from image or table tools.

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?

It gives clear context for when insertion is appropriate (native chart from data, not an image) and lists explicit refusals, but it never names sibling tools like update_chart_data or list_charts as alternatives for existing charts. That keeps it at 'clear context' rather than explicit alternative routing.

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