tv_indicator_show

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

The description repeats the destructiveHint annotation by saying 'DESTRUCTIVE: changes chart visibility,' but adds no further behavioral context (e.g., what happens if the indicator is already visible, error states, or side effects). With annotations already providing the destructive flag, the description contributes minimally.

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 two sentences with zero waste. The first sentence states the purpose, the second flags destructiveness. Perfectly concise for a simple tool.

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?

For a simple one-parameter tool with annotations already covering safety, the description sufficiently explains the action and state change. No output schema exists, but the return value is trivial. Slightly higher score because there is no missing critical information.

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 input schema covers the parameter nameOrIndex with 100% description coverage. The description adds no additional meaning beyond what the schema already provides (e.g., 'by legend name or zero-based index' vs schema's 'Indicator legend name or zero-based index'). Baseline score of 3 is appropriate.

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 (show), the resource (previously hidden indicator), and the selection method (legend name or zero-based index). It distinguishes from siblings like tv_indicator_hide and tv_indicator_remove by focusing on reversing a hide operation.

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?

The description implies that this tool is used to show a hidden indicator, but it does not explicitly state when to use it versus alternatives like tv_indicator_hide or tv_indicator_remove. No guidance on prerequisites or when not to use it.

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