list_movies_wanted

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no meaningful behavioral context beyond restating the endpoint; it does not mention pagination behavior, filtering semantics, or any other operational traits.

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 and front-loaded with the summary, followed by the endpoint and a short Args list. There is no wasted text, though the opening phrase 'List movies wanted subtitles' is grammatically awkward.

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?

Given that all parameters are optional and an output schema exists, an agent can invoke this tool without arguments and interpret the response. Still, the meaning of 'wanted' and the exact role of radarrid are under-specified, and there is no usage guidance to help select the tool confidently.

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%, so the Args section is the only source of parameter meaning. It labels start and length as paging controls and radarrid as 'Movies ID to list', which adds some value beyond the schema's bare names and types. However, the radarrid description is ambiguous and does not clarify that it is an array or how multiple IDs behave.

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 clear action ('List') and resource ('movies wanted subtitles'), which distinguishes it from sibling tools like list_movies, list_movies_blacklist, and list_movies_history. However, the phrasing 'wanted subtitles' is slightly awkward and does not explicitly explain what 'wanted' means in this context.

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 about when to use this tool versus alternatives such as list_movies, list_movies_history, or list_episodes_wanted. The description only provides the endpoint and parameters, with no exclusions, prerequisites, or selection criteria.

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