romaco_reset_view

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool resets to auto-fit all data, implying it overrides manual zoom/pan, but it does not disclose potential side effects such as whether it affects other chart states (e.g., indicators, drawings, multiple panes) or if it is destructive. More detail would be needed for full transparency.

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 long, front-loaded with the core action, and contains no redundant or superfluous words. Every sentence serves a purpose.

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 (no parameters, no output schema, single action), the description is largely complete for its intended use. However, it could be improved by noting whether the reset applies to all panes or just the current pane, and whether it preserves any user-applied settings (e.g., indicators).

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?

There are no parameters, so the schema description coverage is 100% and the baseline is 4. The description adds no additional parameter info, which is acceptable since there are none to describe.

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 action ('Reset the chart view') and the specific behavior ('auto-fit all available data'). It distinguishes from sibling tools like romaco_set_zoom (manual zoom) and romaco_go_to_timestamp (navigation), making the purpose unambiguous.

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 explicitly tells when to use the tool ('Use after zooming or panning to return to the default overview'). It provides clear context for usage but does not mention when not to use it or explicitly contrast with alternatives, though the sibling context implies differentiation.

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