get_stochrsi

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

With no annotations provided, the description carries full burden. It only describes the algorithmic nature (applying stochastic to RSI) but fails to disclose behavioral traits such as whether it is read-only, data requirements, rate limits, or output characteristics beyond the indicator meaning.

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 very short (one sentence) and direct, but it is not well-structured: it compresses the definition and a comparative note without clear separation. It earns no extra credit for conciseness beyond minimalism.

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?

Given the tool has six parameters, no annotations, and an output schema that is not referenced, the description lacks essential completeness. It explains the indicator concept but omits parameter roles, return structure, and usage context, leaving significant gaps for correct 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?

The schema has 0% parameter descriptions, and the description adds no meaning or context for any of the six parameters (fastd, fastk, limit, period, symbol, interval). The AI agent must rely solely on parameter names and defaults, which is insufficient.

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 computes Stochastic RSI by applying stochastic to RSI, and distinguishes it from RSI by noting higher sensitivity. This is specific enough given the large set of sibling technical indicators.

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 hints at when to choose this over RSI ('More sensitive than RSI'), but does not provide explicit guidance on when to use it versus other stochastic or oscillatory indicators among the siblings. No when-not-to-use or alternative recommendations.

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