tv_get_quote

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

No annotations are present, so the description carries the full burden. It usefully discloses the output shape (last OHLCV bar plus percentage change), but it does not mention data delay, exchange handling, or how the interval parameter affects the returned bar. Acceptable but not rich.

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?

Single sentence, front-loaded, and free of filler. Every phrase earns its place by specifying the object, the timeframe, and the included data.

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?

For a simple 3-parameter read tool, the description gives the core return fields, but with no output schema and no annotations it should also clarify interval/exchange behavior and the reference period for the percentage change. Adequate with clear gaps.

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 coverage is only 33%: only 'symbol' has a description, while 'exchange' and 'interval' are undocumented. The description adds no meaning for exchange or interval and does not compensate for the low coverage.

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 uses a specific verb ('get'), names the resource ('latest price quote for a symbol'), and states the exact payload ('last OHLCV bar plus percentage change from the previous bar'). The words 'latest' and 'last bar' clearly distinguish it from tv_get_historical_data and the other siblings.

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 obtaining a current snapshot rather than historical data or indicators, but it never explicitly states when to choose this tool over its siblings. There are no exclusions or alternative routing hints.

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