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

The description adds workflow behavior beyond the annotations: the operation changes the chart being built, and chart_link must be called afterward for the result to be openable. It also tells the agent to source instanceId from chart_state, which is useful behavioral context. It does not contradict the annotations.

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?

Three short sentences are front-loaded with the core action, then the parameter source, then the required follow-up workflow. Every sentence earns its place and there is no 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?

For a one-parameter mutation with minimal annotations, the description covers the action, the parameter source, and the essential follow-up (chart_link). It does not cover failure modes or explicitly rule out sibling tools, but an agent has enough to invoke it correctly.

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 supply meaning for the only parameter. It does so by explaining that instanceId comes from chart_state, giving the agent a concrete way to obtain the value. It does not describe exact format, but the schema already gives the type and required status.

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 uses a clear action ('Take an indicator off the chart') and identifies the resource and the key input source ('instanceId from chart_state'). It is easy to understand, though it does not explicitly distinguish removal from the sibling chart_toggle_indicator, so it is not fully differentiated.

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?

It gives clear usage context: this mutates the chart being built and should be followed by chart_link so the person can open the chart. It does not explicitly state when to prefer this over chart_toggle_indicator or chart_update_indicator, so it lacks exclusions.

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