add_chart_series

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

Discloses refusal condition and defaults, but doesn't specify prerequisites (chart existence), return value, or required permissions. With no annotations, more transparency would be beneficial.

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?

Four sentences, clear front-loading, no redundant information. Could be slightly more streamlined but effective.

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?

Covers core behavior and error condition, but misses prerequisites (chart existence), return value, and broader usage context. Adequate but not comprehensive given no output schema.

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?

Adds significant meaning beyond schema: explains value_field's role in Y expression, defaults for series_type and series_subtype, and combo chart capability. Only path and chart_name are left implicit.

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 action: 'Append a new <ChartSeries> to a named chart.' It explains key parameters and distinguishes from siblings like set_chart_series_type and remove_chart_series by focusing on adding new series.

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 context is implied (adding new series, refusal if exists), but no explicit guidance on when to use this tool versus alternatives like set_chart_series_type or set_chart_series_action.

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