tv_indicator_remove

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

Adds 'DESTRUCTIVE' which aligns with destructiveHint annotation. No additional behavioral details beyond what annotations and schema provide.

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?

One sentence plus one word, no wasted text, front-loaded with action. Very concise.

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 functionality adequately for a simple tool. Could mention permanence or chart scope, but annotations fill some gaps.

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 coverage 100% and description echoes schema ('exact legend name or zero-based index'). Adds minimal extra value like 'exact' but no format or range details.

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?

Clearly states the action (remove), target (indicator from chart), and identification method (legend name or index). Distinguishes from sibling tools like tv_indicator_hide or tv_indicator_show.

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?

Provides identification method but no explicit guidance on when to use this vs alternatives (e.g., hide vs remove). Lacks when-not or prerequisites.

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