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 behavior burden. It does disclose return values ('returns the chart name and title'), which is useful since no output schema exists, but it says nothing about where the chart is placed, whether a new worksheet is created, permission requirements, or reversibility of the mutation.

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 tight sentences with the core action front-loaded. The chart-type enumeration is somewhat redundant with the schema enum and incomplete against it, which slightly dilutes the value-per-sentence.

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 5-parameter creation tool with no output schema, the description covers the action and the return values. It is nearly complete, but leaves chart placement behavior (default sheet, insertion position) implicit, which an agent may need to know.

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 reinforces that the data comes 'from a range' and that title is settable, but adds no syntax, defaults, or format detail beyond what the schema already documents.

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?

States a specific verb and resource ('Create a chart from a range') and enumerates supported chart types, which distinguishes it from siblings like add_table or add_conditional_format. However, the chart-type list is a partial subset of the schema enum (omitting ColumnStacked100, BarStacked100, PieStacked, AreaStacked), which could briefly mislead.

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?

Usage is implied by the verb and the 'from a range' phrasing, but there is no explicit when-to-use/when-not guidance and no mention of the related sibling edit_slide_chart or how this differs from other Excel mutation tools.

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