extract_indicators

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

Discloses it reads public historical candles via yfinance, cannot place trades, and defaults from TradingView window if omitted. Clearly read-only and safe. No annotations exist, so description carries full burden and does well.

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?

Very concise: three sentences covering key points. Front-loaded with action and indicators. No extraneous information.

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 output schema exists and complexity of indicators, description covers data source, excluded actions (no trading), and default behavior. Could mention that lookback is the number of candles for computations.

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?

Briefly explains symbol and interval default behavior, but does not describe the 'lookback' parameter. Schema coverage is 0%, so some compensation is provided but incomplete.

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?

Clearly states it computes a technical-indicator bundle, listing specific indicators (RSI, EMA, MACD, etc.) and signals. Distinguishes from siblings (get_symbol, get_watchlist, etc.) by being the only tool computing 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?

Implies use when technical indicators are needed, but no explicit guidance on when to use vs alternatives or when not to. For example, no mention of alternative data sources or tools for other types of analysis.

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