list_settings_discover_reset

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

The description says 'Reset all discover sliders,' which implies a mutating operation, but the annotations declare readOnlyHint=true and destructiveHint=false. This is a direct contradiction. The description also fails to disclose what 'reset' means—whether sliders return to defaults, whether confirmation is needed, or what side effects occur.

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 core instruction is one clear sentence, and the HTTP endpoint line is short. The description is not bloated, but the endpoint line adds little beyond what the tool name and action already imply.

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?

The description is too sparse for a tool that performs a reset. It does not specify what 'reset' entails, whether it affects all users or just the current one, or whether it is reversible. The annotation contradiction further undermines completeness, even though an output schema exists and no parameters are needed.

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 and 100% schema description coverage, so there is nothing for the description to clarify. The baseline of 4 for parameterless tools is appropriate; any parameter explanation would be superfluous.

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 states a specific verb and resource: 'Reset all discover sliders.' This clearly communicates the action and object, and the word 'all' distinguishes it from per-slider update or delete operations. However, it does not explicitly differentiate itself from sibling tools like update_settings_discover_by_slider_id or delete_settings_discover_by_slider_id.

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 guidance about when to use this tool versus alternatives. It does not mention that update_settings_discover_by_slider_id is for changing individual sliders, or that list_settings_discover is for viewing current settings. The usage context is only implied by the verb 'reset.'

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