tv_layout_reset

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

Description adds 'removes indicators and drawings' beyond the destructiveHint annotation, providing concrete behavioral context. However, it does not mention impact on other settings like timeframes.

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?

Two short, front-loaded sentences with zero waste. The warning 'DESTRUCTIVE' is prominent.

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?

For a zero-parameter, simple reset tool with annotations and no output schema, the description sufficiently covers purpose and primary effect. All necessary context is present.

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?

No parameters present, so baseline 4 applies. Description adds no parameter info because none exist.

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 'Reset the active chart layout to its default/empty state' with a specific verb and resource, clearly distinguishing from sibling layout tools like tv_layout_list or tv_layout_switch.

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?

Description implies use when wanting to clear the layout but does not provide explicit when-not-to-use or alternatives. The destructive warning is helpful but not comprehensive.

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