seerr_update_discover_slider

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

Annotations already indicate readOnlyHint=false, and the description adds 'this modifies your Seerr instance', which is consistent with the annotation and provides a side-effect warning. However, it doesn't disclose specific consequences beyond the vague 'modifies', such as which fields get overwritten or whether changes are reversible.

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 filler. It efficiently conveys the core action and side-effect, earning every word without unnecessary elaboration.

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?

With a nested 'body' parameter and 0% schema coverage, the description leaves the agent without enough information to construct a payload. The output schema exists but doesn't help with input construction. It also doesn't explain what a 'slider' is or what fields the body should contain, making the tool incomplete for correct invocation.

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?

Schema description coverage is 0%, and the description provides no explanation of the 'body' object or the 'slider_id'. The only hint is the tool name itself. Since the description doesn't compensate for the missing schema descriptions, parameter semantics are severely lacking—an agent would not know what to put in the body or how to identify the slider.

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 'Update a single slider' with a specific verb and resource. The emphasis on 'single' distinguishes it from the sibling tool seerr_update_discover_sliders (plural), and the 'WRITE' label reinforces the action. This is a clear, unambiguous purpose.

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?

No guidance is provided on when to use this tool versus alternatives like seerr_update_discover_sliders, seerr_list_discover_sliders, or seerr_delete_discover_slider. There is no mention of prerequisites, selection criteria, or scenarios where a single slider update is appropriate.

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