seerr_add_discover_slider

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

The description repeats the write operation implied by annotations (readOnlyHint=false) but adds no deeper behavioral context. It doesn't mention authentication, side effects, or how existing sliders are affected. The 'WRITE' declaration is redundant given the annotation.

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 short, but the 'WRITE' phrase is redundant with the readOnlyHint annotation, wasting a few words. It is neither verbose nor well-structured, carrying a single vague sentence.

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?

This is a write tool with an unstructured body parameter and no parameter guidance. The description fails to explain what a slider is, what fields are needed, or how the operation interacts with existing sliders, leaving the agent without enough context to invoke it correctly.

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 input schema defines a free-form 'body' object with zero documentation, and the description provides no hints about required fields or structure. Since schema description coverage is 0%, the description must compensate but doesn't, making parameter construction impossible.

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 names a specific verb and resource ('Add a new slider') and notes it's a write operation, distinguishing it from sibling list/update/delete tools. However, it doesn't clarify what kind of slider (e.g., discover, genre) beyond the tool name.

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 given on when to use this tool versus alternatives like seerr_update_discover_slider or seerr_reset_discover_sliders. The only hint is that it modifies the instance, which is insufficient for choosing between tools.

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