seerr_import_jellyfin_users

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

Annotations already indicate readOnlyHint=false, so the description's 'WRITE' reinforces but adds little beyond that. It adds the context that the operation modifies the Seerr instance, but it does not disclose what exactly changes (e.g., creates users, potential duplicates) or any side effects. This is some added value but not rich behavioral disclosure.

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 two clauses that both add relevant information. It front-loads the action and highlights the write nature. No wasted words.

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?

The tool has a simple purpose but the body parameter is undocumented, and the description does not mention any prerequisites (e.g., Jellyfin must be configured) or potential side effects. The output schema exists so return values are covered, but the incomplete parameter info and lack of behavioral context keep it from being complete.

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 one parameter 'body' with no description and 0% coverage, so the description must compensate. It does not mention the body parameter at all, leaving its purpose and any allowable fields entirely unexplained. Since the tool has an optional body parameter but the description implies no parameters are needed, the agent has no guidance on what to pass.

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 action ('Import all users from Jellyfin') with a specific verb and resource, and it explicitly notes it modifies the Seerr instance. The tool name and description distinguish it from the similar sibling 'seerr_import_plex_users' by specifying Jellyfin.

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 implies usage by stating what the tool does, and the 'WRITE: modifies' warning gives some context. However, it does not explicitly mention when to use this versus alternatives (e.g., the sibling import for Plex) or provide any exclusions or prerequisites, so the guidance is only implied.

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