seerr_delete_discover_slider

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

The description repeats 'DESTRUCTIVE: this deletes data', which is already captured by destructiveHint=true annotation. It adds no extra behavioral context such as irreversibility, cascading effects, or permission requirements, beyond what the annotations already convey.

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 first sentence is lean and front-loaded, but the second sentence ('DESTRUCTIVE: this deletes data.') is redundant with the annotations and adds no value. Every sentence should earn its place, and this one does not.

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 simple one-parameter delete with annotations and an output schema, the description is minimally adequate. However, it lacks any usage context or caveats (e.g., whether the deletion is permanent or requires admin rights), leaving some gaps despite the structured data.

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 only echoes 'by ID', which adds little beyond the parameter name 'slider_id' and type integer in the schema. It does not explain how to obtain the ID or any constraints, failing to compensate for the low schema coverage.

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 'Delete slider by ID', specifying the action (delete), resource (slider), and identifier (ID). This distinguishes it from sibling tools like seerr_list_discover_sliders, seerr_update_discover_slider, and seerr_add_discover_slider.

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 such as seerr_reset_discover_sliders or seerr_update_discover_slider. It simply states the action without contextual exclusions or alternative recommendations.

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