seerr_reset_discover_sliders

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description is not required to restate them. However, it adds no extra behavioral context beyond the action itself, such as what 'reset' does to custom slider configurations, whether it is reversible, or if it affects user preferences.

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 short sentence that is front-loaded with the action and subject. Every word contributes meaning, with no irrelevant detail or repetition.

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?

Despite having an output schema and zero parameters, the description is incomplete for a mutation tool that resets 'all' sliders. It does not explain what 'reset' entails, potential impact on user-specific settings, or any warnings about irreversibility, leaving an agent with insufficient context to safely decide to invoke it.

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 tool has zero parameters, so the baseline of 4 is appropriate. The description does not need to explain parameter semantics, and the empty schema is fully covered.

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 'Reset all discover sliders' uses a specific verb ('Reset') and a specific resource ('all discover sliders'), clearly distinguishing it from sibling tools like list, update, add, and delete. The scope ('all') also clarifies it is a bulk operation.

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?

There is no guidance on when to use this tool versus alternatives such as update_discover_sliders or update_discover_slider. The description does not mention prerequisites, side effects, or cases where this should be preferred.

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