Strata candles

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds 'bounded' and 'time-bucketed' as useful behavioral context, but it does not disclose return format, pagination, or edge-case behavior.

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 a single front-loaded sentence with no filler. Every phrase—'bounded', 'time-bucketed', 'one opaque Strata market ID'—adds meaningful context.

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?

The schema and annotations are rich, and the description conveys the essential read-only, single-market, candle-aggregation behavior. Since there is no output schema, return format is left implicit, but 'candles' is a standard trading concept and the description covers the core operation well.

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?

With 0% schema description coverage, the phrases 'bounded time-bucketed' and 'one opaque Strata market ID' add meaning: fromMs/toMs delimit the range and resolutionSeconds controls bucket width. However, the description never explicitly maps or explains individual parameters beyond these allusions.

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 names a specific verb ('Read'), a resource ('candles'), and a clear scope ('one opaque Strata market ID'). This distinguishes it from sibling market-data tools like strata_bbo, strata_trades, or strata_marks.

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 use when bounded, time-bucketed candle data for a single market is needed. It provides no explicit when-not-to-use guidance or named alternatives among the many strata_* data tools.

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