seerr_create_watchlist

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

Annotations already declare readOnlyHint=false, and the description's 'WRITE: this modifies your Seerr instance' is largely redundant. No additional behavioral details are provided, such as duplicate handling, required media fields, or side effects beyond a generic 'modify'.

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 very short, with the main clause at the start. The 'WRITE:' prefix is slightly awkward but does not add significant length. It is efficient, though a bit cryptic.

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?

Despite the presence of an output schema, the input contract is entirely opaque. There is no mention of what media identifiers or properties are needed in 'body', nor any operational context. An agent cannot reliably determine how to construct a valid request from this description alone.

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?

The schema has a single 'body' object with 0% coverage and no descriptions. The description does not explain what the body should contain (e.g., media ID, media type), leaving the primary parameter completely unspecified. This is a critical gap for an agent to invoke the tool correctly.

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 verb 'Add' and the resource 'media to watchlist', which is specific and distinguishes it from sibling tools like seerr_delete_watchlist and seerr_get_user_watchlist. The 'WRITE' label emphasizes the mutating nature of the operation.

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 is provided on when to use this tool versus alternatives such as create_request or the watchlist-related siblings. It does not mention prerequisites, authentication, or any context in which this tool should be preferred.

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