list_discover_genreslider_tv

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the GET endpoint and scope, but does not disclose details such as response contents, language matching behavior, pagination, or auth requirements.

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 compact, front-loaded with the core purpose, and organized with endpoint and args. There is no filler or repetition of the tool name.

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 read-only GET with one optional parameter, an output schema, and rich safety annotations, the description is largely sufficient. It is missing only minor context such as what 'genre slider data' specifically contains and accepted language code formats.

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?

With 0% schema description coverage, the description needed to explain the parameter. It labels 'language' as a query parameter, which adds transport-level meaning beyond the schema, but it does not specify format, allowed values, or examples, so compensation is only partial.

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 ('Get') and resource ('genre slider data for TV series'), and includes the endpoint. The 'TV series' qualifier clearly differentiates it from sibling list_discover_genreslider_movie and other discover tools.

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 implies when to use the tool—when TV genre slider data is needed—but gives no explicit comparison with alternatives like list_discover_genreslider_movie or list_discover_tv, and no exclusions. It leaves some routing to inference from the tool name.

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