tradingview_quote

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

Discloses 15-min delay, returned data fields, and emptry ticker handling beyond the annotations (readOnlyHint, destructiveHint, openWorldHint). Adds context about data freshness and error recovery.

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?

Three sentences, front-loaded with purpose and key info, no extraneous words. Efficient and clear.

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 purpose, delay, returned fields, alternative tool, and error recovery. No output schema needed given the description. Complete for a simple quote tool.

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 already describes 'tickers' with examples (100% coverage). Description reinforces format but doesn't add new semantic meaning beyond schema. Acceptable baseline.

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 'get a 15-minute delayed quote for one or more stock tickers', specifying the verb, resource, and key characteristic (delay). Distinguishes itself from siblings like tradingview_scan and finnhub_quote.

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?

Explicitly tells when to use (for delayed quotes), when not to use (if real-time needed, use finnhub_quote), and provides retry advice with exchange prefix. No ambiguity.

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