plex_get_unwatched

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

No annotations provided; the description only states basic functionality without disclosing behavioral traits such as pagination behavior, returned metadata, auth requirements, or rate limits.

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 extremely concise, with a single purpose line and brief parameter explanations. No wasted sentences, front-loaded with core purpose.

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 an output schema present, the description does not need to detail return format. However, it omits context like whether it returns episodes or series-level data, or any prerequisites. Adequate for a simple list tool.

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 coverage is 0%, so the description adds value by explaining 'library_key' is optional and referencing 'plex_get_libraries', and 'limit' indicates max results. However, details like format or allowed values are missing.

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 the tool retrieves unwatched movies or series, using a specific verb ('Récupère') and resource, distinguishing it from siblings like 'plex_get_watched' and 'plex_get_recently_added'.

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 hints at using 'plex_get_libraries' to find library keys, but lacks explicit guidance on when to use this tool versus alternatives like 'plex_get_watched' or 'plex_get_recently_added'.

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