chart_scroll_to_date

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

No annotations are provided, so the description must fully disclose behavior. It states that the chart view is centered on a date, implying a view mutation, but does not detail edge cases, prerequisites, or whether the visible range is adjusted. For a simple navigation action, this provides some transparency but lacks depth.

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 unnecessary words, perfectly concise.

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 low complexity (1 parameter, no output schema), the description sufficiently explains the tool's function. It could benefit from noting prerequisites or behavior relative to sibling tools but is adequate for this scope.

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 single parameter 'date' is fully documented in the schema with formats (ISO string or unix timestamp). The description does not add additional information about parameter semantics, so it meets the baseline for 100% 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 uses a specific verb 'jump' and 'center' with the resource 'chart view', clearly indicating the action of navigating to a date. This distinguishes it from other chart_* tools like chart_set_symbol or chart_set_timeframe.

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 usage for when the user wants to navigate the chart to a specific date but does not explicitly mention alternatives or exclusions. Context from sibling tools (e.g., chart_set_visible_range) might help but is not referenced in the description.

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