edit_slide_chart

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that all OOXML artifacts are generated automatically and lists supported chart types, but it omits overwrite/replacement semantics, permission requirements, failure modes, and response behavior for this mutation tool.

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 two efficient sentences with no wasted text. The core creation action is front-loaded and the second sentence adds relevant supported-type context.

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 complex 8-parameter nested mutation tool with no annotations and no output schema, the description covers creation and supported chart types but leaves gaps around usage selection, overwrite behavior, and return values. The schema handles parameter details, but the description is not fully complete for the tool's complexity.

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 schema already documents all 8 parameters, including nested series, options, position, and presentationId. The description adds only chart type and multiple-series context, which is already represented in the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: 'Create a chart on a slide from structured data,' and enumerates supported chart types and multiple series. However, the tool name says edit_slide_chart while the description says create, and it does not explicitly distinguish this from the raw XML sibling edit_slide_xml.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The phrase 'from structured data' implies it is intended for data-driven chart creation rather than raw OOXML editing, but the agent must infer that versus edit_slide_xml.

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