indicator_bbands_direct

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

The description mentions fetching K-line data and computing bands, but does not disclose whether it is read-only, any rate limits, data source implications, or side effects. With no annotations, the description provides insufficient behavioral context.

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?

Extremely concise: two sentences with no extraneous information. Front-loaded with purpose and defaults, efficiently using space.

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?

With 5 parameters and no output schema, the description is too brief. It does not explain the return format, how 'direct' differs from the non-direct sibling, or any operational details needed for proper invocation.

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?

Input schema covers all parameters with descriptions (100% coverage). The description reinforces default values (20 period, 2 stddev) but adds minimal additional meaning beyond the schema. Baseline 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 it computes Bollinger Bands directly from K-line data, with defaults of 20 periods and 2 standard deviations. However, it does not explicitly differentiate from the sibling 'indicator_bbands' (non-direct), leaving ambiguity about when to use this variant.

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?

No guidance is provided on when to use this tool over alternatives (e.g., 'indicator_bbands' or other indicators). The description lacks usage context, prerequisites, or exclusions.

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