get_intraday_candles

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds valuable context about the real-time quote entitlement requirement (code 1032), which is not captured in annotations or schema. This helps the agent anticipate authorization needs.

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 tight, front-loaded sentences. The first states the core function and parameters; the second adds a critical entitlement requirement. No filler or redundancy.

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 candle-retrieval tool, the description covers purpose, bucket parameter, time range, and entitlement. An output schema exists, so return values are documented elsewhere. Some details like maximum days or data freshness are omitted, but not essential for basic usage.

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 zero parameter descriptions. The description compensates by explaining the key parameters: 'period_minutes' for bucketing and 'last N days' for the 'days' parameter. 'symbol' is self-evident from context. Defaults are in 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 the tool retrieves intraday OHLC candles, specifies the bucketing parameter (period_minutes), and the time range (last N days). This distinguishes it from siblings like get_daily_candles and get_tick_data.

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 provides clear context for when to use this tool (intraday aggregated candlestick data) and mentions the entitlement prerequisite. It doesn't explicitly name alternative tools or exclusions, but the context is sufficient for an agent to differentiate.

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