veroq_candles

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

No annotations provided, but the description adds return format ('Array of candles with date, open, high, low, close, volume. Latest candle highlighted') and cost ('2 credits'). It does not contradict any annotations.

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?

Well-structured with distinct sections for purpose, usage, returns, cost, and example. Every sentence is relevant, no fluff. Front-loaded with the core action.

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?

All parameters are documented in the schema, and the description outlines the return data and cost. Given the tool's simplicity and the rich sibling list, the description provides enough context 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?

Schema descriptions cover all parameters (100%), but the description provides an example usage with typical values ('symbol': 'AAPL', 'interval': '1d', 'range': '3mo'), adding practical value beyond the schema.

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 'Get OHLCV candlestick data for a stock ticker', specifying the verb, resource, and scope. It distinguishes from siblings like veroq_technicals, which offers pre-computed 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?

Includes explicit 'WHEN TO USE' section and an alternative sibling ('Use veroq_technicals for pre-computed indicators'), providing clear guidance on when to use this tool versus others.

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