list_providers_movies

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

Annotations indicate readOnlyHint, idempotent, and non-destructive, so the tool is a safe read operation. The description adds the endpoint and 'manually' but does not explain output structure, pagination, or error behavior. Given annotations cover safety, the burden is partly met but more context would help.

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 short and includes the endpoint and ARGS, but it is not well-structured for an agent. It reads like code comments rather than prose meant for tool selection. The first line is a high-level hint, but the rest is minimal and lacks a clear separation of purpose and usage.

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?

This is a search tool with an output schema, but the description does not explain what providers are returned, how results are ordered, or how to interpret the output. Given the complexity of subtitle search, more context such as required parameters or typical usage would be necessary for correct invocation.

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 description must compensate. It mentions 'radarrid: Movie ID' but gives no explanation of how it is used (e.g., limit to a specific movie, required for searching?). Without more detail, the agent may not understand the parameter's role.

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 it searches for movie subtitles and includes the endpoint. However, the tool name 'list_providers_movies' suggests listing providers for movies, not searching subtitles, so there is ambiguity about what it actually returns. It is not clear how it differs from list_providers, list_subtitles, or other listing 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?

No guidance on when to use this tool versus alternatives. The description mentions 'manually' but gives no context for when manual search is appropriate or what the tool returns compared to list_subtitles or list_providers. No exclusions or alternative comparisons are provided.

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