office_chart_tool

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

No annotations are provided, so the description carries the full behavioral burden, yet it only covers parameter formatting. It never states that the tool mutates the file in place, whether an existing chart is overwritten, whether the file must already exist, or what errors occur on malformed ranges. Side-effect disclosure is largely absent.

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 purpose is front-loaded in one sentence, then the two operating modes are described in a clearly separated paragraph with examples. Every sentence carries useful formatting information with no obvious filler.

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?

With 11 parameters and no annotations, the description covers the file-type-specific parameter usage reasonably but omits sheet/slide selection semantics, title, and series_name behavior. An output schema exists so return values need no explanation, but for a mutation tool of this parameter count the coverage is only adequate.

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 compensate, and it does for the hardest parameters: it explains data_range, categories_range, anchor, and the pptx values/categories comma-list format with concrete examples (B1:B4, A2:A4, E2, Jan,Feb / 10,12). It leaves path, sheet, slide, title, and series_name undocumented, so it is not fully complete.

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 gives a concrete verb ('Add') and resource ('bar, line, or pie chart') and names both target containers ('xlsx sheet or pptx slide'). It does not explicitly differentiate itself from siblings like office_slide_tool or office_sheet_tool, but the chart-specific scope is unmistakable.

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 through the xlsx-vs-pptx branching (which parameters apply to which file type), but there is no explicit when-to-use/when-not statement or pointer to alternatives. An agent can infer the mode from the file, but the guidance is not spelled out as a rule.

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