chart_set_timeframe

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to indicate whether this is a read or write operation, whether it affects other chart state, or if there are side effects like resetting visible range. The description adds minimal behavioral context beyond the schema.

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, clear sentence with no wasted words. It is efficient and front-loaded with the action, though it could be slightly more descriptive without losing brevity.

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?

Given the tool's simplicity (1 param, no output schema), the description is somewhat adequate but lacks critical context such as whether the change is reversible, what the visual feedback is, or if it requires a chart to be already set (chart_set_symbol). The sibling tools suggest a trading platform context, but missing usage coordination hurts completeness.

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 coverage is 100% and 1 parameter has enum values, so the baseline is 3. The description does not add any meaning beyond what the schema already provides, but since coverage is complete, no deduction is needed.

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 verb 'Change' and the resource 'chart timeframe/resolution', which is specific enough to distinguish it from siblings like chart_set_symbol or chart_set_visible_range. It does not explicitly distinguish from data_get_ohlcv, but the resource is distinct.

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 no explicit guidance on when to use this tool vs alternatives, such as when to change timeframe vs getting the current state. Among siblings, chart_get_state and data_get_ohlcv are related, but no exclusions or context are given.

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