seerr_list_media

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

The description discloses no behavioral traits beyond the readOnlyHint annotation. It adds no information about pagination, filtering semantics, response shape, or any side effects, though the read-only annotation already covers safety.

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?

While the description is short, it is under-specified rather than concise. 'Get media' doesn't earn its place because it conveys almost no useful information.

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 tool with 4 parameters and zero schema documentation, this description is entirely inadequate. It fails to complete the picture of what the tool does, what parameters mean, or how it relates to the large sibling toolset.

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?

All 4 parameters (skip, sort, take, filter) have no schema descriptions and 0% coverage. The description gives no explanation of these parameters or how they affect the request, failing to compensate for the missing schema documentation.

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 'Get media' is a tautology of the tool name 'seerr_list_media'. It provides no specifics about what 'media' refers to, whether it's a list or detail, or how it differs from sibling tools like seerr_get_movie or seerr_list_discover_trending.

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?

There is no guidance on when to use this tool versus alternatives. The description lacks context about use cases, prerequisites, or situations where another sibling tool would be more appropriate.

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