批量指标

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

annotation已经标记readOnlyHint和openWorldHint，描述不需要重复安全说明。描述额外补充了“直接拉K线”“只算最新值”“一次网络往返间接完成多个指标计算”，这些不是schema能直接看出的行为上下文，很有价值。

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?

在存在输出schema、readOnlyHint且参数schema已含default/enum/range的情况下，描述已经覆盖了“何时用、算什么、有哪些可选开关和最大收益”，没有明显缺口。选择正确的所需信息已足够。

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，覆盖率为0%，而描述主动讲解了默认指标周期和includeATR/includeADX/includeStoch三个布尔参数的含义。但没有说明limit对指标 lookback 窗口的具体影响，也没显式对应symbol/interval，所以扣掉一分。

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?

明确说明动作是“单次拉取K线，批量计算”，并列出默认计算 RSI(14)+MACD(12/26/9)+BBands(20/2)，可选用ATR/ADX/Stoch。它与indicator_rsi、indicator_macd、indicator_bbands等单个指标工具显著区分，不依赖打开schema也知道这是批量版。

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?

清楚写明“替代逐个调用 3-6 次网络往返”，即当需要多个指标时优先使用本工具。缺点是没有显式说明“如果只需一个指标，应改用单个indicator_*”，所以不算完全满足when-not的边界。

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