get_daily_candles

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

The description adds critical behavioral context beyond the annotations by disclosing the entitlement prerequisite and the specific error code 1032. The annotations only declare read-only, open-world, and idempotent behavior, so this auth/failure information is valuable and does not contradict the 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?

The description is two sentences: the first states the core purpose, the second adds a necessary prerequisite. It is front-loaded, concise, and free of redundancy, earning its place.

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 read-only data tool, the description covers the main action, the key parameter, and a critical failure condition. The presence of an output schema handles return details, so nothing essential is omitted, though a note about timezone or data adjustments would have made it slightly more complete.

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?

The description explains that the `days` parameter controls the lookback window ('last N days'), which adds meaning to a parameter that otherwise has no schema description. The `symbol` parameter is left implicit but is self-evident from the tool name, so the description provides adequate compensation for the 0% schema 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 clearly states the tool retrieves daily OHLC candles for the last N days, using a specific verb and resource. This distinguishes it from sibling tools like get_intraday_candles or get_candle_data_range, which cover different timeframes or ranges.

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 by noting the real-time quote entitlement requirement and the failure code 1032, which informs when the tool can be used. However, it does not explicitly mention alternatives or when not to use it, so it stops short of a full when-to-use guide.

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