seerr_get_user_jellyfin

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

The readOnlyHint annotation already indicates a safe read operation. The description adds no additional behavioral context such as error handling, return format, or whether the Jellyfin ID must exist. It does not contradict the annotation, so a baseline score of 3 is appropriate.

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 a single short sentence, 'Get user by Jellyfin user ID,' which is appropriately concise and front-loaded with the key action and resource.

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 the simple single-parameter read-only tool and the presence of an output schema, the description covers the core purpose but lacks context about when to use this tool versus other user lookup tools. It is minimally complete but leaves the user to infer distinctions from sibling tool names.

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 0% description coverage, so the description must compensate. However, 'by Jellyfin user ID' essentially restates the parameter name 'jellyfin_user_id' without adding meaningful details like format, requiredness, or distinction from other user ID types. It provides minimal semantic value beyond what the schema already reveals.

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's action ('Get user'), the resource ('user'), and the lookup key ('by Jellyfin user ID'). This distinguishes it from sibling tools like seerr_get_user (likely by internal ID) and seerr_list_user (list all users).

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 when you have a Jellyfin user ID and need the corresponding user object. However, it does not explicitly mention alternatives or when not to use this tool, such as when you have an Overseerr user ID instead of a Jellyfin ID.

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