strategy_rsi2

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

No annotations are provided, so the description carries the full burden. It discloses the return value meanings, which is helpful. However, it does not state that this is a read-only computation, does not mention data source (OHLCV), and leaves ambiguity about how period interacts with '2-period RSI'.

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 a single focused sentence followed by an output legend. Every element contributes meaning, and it is front-loaded with the strategy name and purpose. No wasted words.

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?

There is a notable ambiguity between the strategy name ('2-period RSI') and the period parameter default (14), which is not explained. The description does not specify how limit, period, and timeframe affect the signal, and there is no output schema or additional context. This could lead to incorrect 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter-level insight beyond the schema. It does not clarify the relationship between the 'period' parameter and the '2-period' description.

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 the tool's function: generates short-term mean reversion signals using a 2-period RSI, with explicit output values (-1, 0, 1). This is specific and distinguishes it from other strategy tools like strategy_macd or strategy_apo.

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 usage for short-term mean reversion scenarios, but does not explicitly mention when to prefer this over other strategies or provide any exclusions. Sibling tools include many strategy variants, so more explicit guidance would help.

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