get_candlesticks

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

Annotations already indicate read-only, open-world, and idempotent behavior. Description adds operational constraints (symbol format, parameter precedence, default/max count) that go beyond annotations, providing comprehensive behavioral context.

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 sections (strategy, critical rules, examples, Args). Front-loaded with purpose and usage. Slightly verbose but all content is valuable given the tool's complexity.

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?

With output schema present, description focuses appropriately on input parameters and usage rules. Covers all necessary details for correct invocation, including defaults, constraints, and examples. No gaps identified.

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 0% description coverage, so description carries full burden. It explains all parameters with default values, allowed values (period), and meaning (symbol format). Adds significant value beyond the schema's titles and types.

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?

Description explicitly states 'Get candlestick (OHLCV) data for any asset class', using a specific verb and resource. It clearly distinguishes from sibling tools which cover different financial data types.

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?

Provides explicit strategy for use (directly invoke with symbol, infer asset_class) and critical rules (symbol format, parameter precedence). Includes examples. Does not explicitly exclude alternative tools but gives enough context for correct invocation.

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