tv_drawing_add_trendline

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

The description labels the tool as 'experimental' and 'best-effort', which indicates instability but does not disclose other behavioral traits like side effects or failure modes. Annotations correctly mark it destructive, but the description adds minimal transparency beyond that.

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 extremely concise—two short phrases—with no superfluous words. It front-loads the key action ('add a vertical trend line') and includes necessary 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?

The description lacks completeness: it describes a UI interaction ('two clicks on the chart pane') which may confuse an AI agent expecting a programmatic API. No return value or prerequisites are mentioned, and the 'best-effort' label adds uncertainty without specifics.

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?

The tool has zero parameters and schema coverage is 100%, so no parameter details are needed. The description appropriately adds no further parameter information.

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 tool adds a vertical trend line via the left drawing toolbar using two clicks, distinguishing it from all sibling tools that perform different functions.

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 or when not to use it. The description only states what it does without context.

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