tradingview_technicals

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

Annotations (readOnlyHint=true) align with read-only nature. Description adds important retry behavior beyond annotations: 'retry with correct exchange prefix'. No contradictions. Could mention data freshness or rate limits.

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?

Two sentences: first defines purpose, second provides critical troubleshooting guidance. No waste; each sentence contributes directly to tool usability.

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?

Covers input and retry behavior well. No output schema, so description could list return structure or example values. However, given sibling richness, the purpose is clear. Minor gap in output details.

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 has 100% coverage with descriptions for both parameters. Description restates that tickers are stock tickers and implies multiple tickers are allowed, but adds no new meaning beyond 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?

Clear verb 'Get' and resource 'technical indicators... for stock tickers'. Lists well-known examples (RSI, MACD, moving averages). Distinguishes from siblings like tradingview_quote (price) and tradingview_scan (screening).

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?

Explicit retry guidance with exchange prefix for empty results. Does not explicitly state when to prefer this tool over siblings, but context from sibling names makes it clear this is for technical indicators. Missing direct comparisons.

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