indicator_bbands

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

由于未提供注解，描述承担了行为透明度的全部责任。描述仅提及输出结构，未说明计算是否具有副作用、权限需求或性能特征（如大数据集的计算复杂度）。

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?

描述由两句话组成，第一句点明功能与输出，第二句给出典型参数。无冗余信息，结构清晰且前置重要内容。

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?

在缺乏输出模式的情况下，描述清晰列出了返回值的四个字段（upper, middle, lower, bandwidth），满足基本理解需求。对于简单的计算工具，信息量已足够。

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?

输入模式对所有3个参数都有描述（values、period、deviationMultiplier），覆盖率100%。描述中的'通常20周期2倍标准差'进一步强化了默认值，但未添加超出模式描述的新含义。

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?

描述明确说明该工具用于计算布林带并返回四个分量（upper, middle, lower, bandwidth），同时给出典型参数（20周期2倍标准差），与同类工具（如indicator_bbands_direct）有区分。

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?

描述未提供何时使用此工具而非其他同类工具的指导，也未说明使用前提或限制条件。仅给出参数默认值，缺乏对比信息。

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