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

With all annotations false, the description carries the burden. It discloses that the tool changes the chart being built and implies a side effect, but it does not mention idempotency, reversibility, or any potential impact on existing indicators or settings. The statement 'This changes the chart you are building' adds some transparency but is thin for a mutating tool.

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 one concise sentence plus an example and a contextual note. The main action is front-loaded, and every sentence adds meaning. There is no fluff, making it efficient and easy to parse.

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 tool has three parameters with one required and two enums, yet the description does not clarify that only symbol is required while exchange and market are optional. It also fails to explain the 'market' parameter, leaving the agent to guess. The effect on the chart is mentioned, but the description is incomplete for a tool with these parameters and no output schema.

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 is 0%, so the description must compensate. It explains the format for symbol and exchange ('as the exchange writes them') and gives an example, but it does not address the 'market' parameter (spot/futures) at all. The description adds value for two of three parameters but leaves the third entirely undocumented.

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 states a clear action ('Point the chart at a market'), names the resource (chart instrument), and provides a concrete example (BTCUSDT on binance). It also explains the effect on the chart being built, distinguishing it from other chart manipulation tools like chart_set_timeframe or chart_set_type by the specific verb and context.

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 when to use this tool (when building a chart and needing to set the market) but does not explicitly compare it to alternatives or state when not to use it. It mentions the chart is linked via chart_link, which gives some context, but there is no exclusionary guidance.

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