insert_line_chart

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

No annotations are present, and the description fails to disclose any behavioral traits such as whether the chart replaces existing content, requires specific permissions, or how errors are handled. The description carries the full burden but provides almost nothing.

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 very short at two sentences, which is concise but lacks depth. It is front-loaded with the purpose but wastes no words. However, the extreme brevity compromises informativeness.

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?

Given the tool has 6 parameters (4 required), no parameter descriptions in schema, and no annotations, the description is severely incomplete. It mentions only the series data format but leaves out critical context for other parameters. The presence of an output schema does not excuse the lack of parameter explanation.

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%, placing full burden on the description. The description partially compensates by showing the `series` parameter format but does not explain `para_id`, `categories`, `width_cm`, `height_cm`, or the `title` parameter. The example is insufficient for complete understanding.

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 'Insert a native line chart,' specifying both the action and the chart type. It distinguishes from sibling tools like insert_bar_chart and insert_pie_chart by naming the chart type explicitly.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., bar or pie charts). There are no prerequisites or context about the document state required for insertion.

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