seerr_login_jellyfin

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

The description explicitly states 'WRITE: this modifies your Seerr instance,' but this is essentially a restatement of readOnlyHint=false. It adds no additional context such as session creation, side effects, or failure behavior. There is no annotation contradiction, but the description fails to go beyond what annotations already convey.

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 sentence of roughly 15 words, making it appropriately sized and front-loaded. The phrasing 'WRITE: this modifies your Seerr instance' is a bit jarring but still concise and without fluff.

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?

For a login operation, the description omits crucial details: expected response layout, session behavior, prerequisites (e.g., Jellyfin must already be configured), and error handling. The presence of an output schema mitigates some ambiguity, but the tool's context is still largely unexplained, especially relative to the many sibling authentication tools.

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 input schema is a generic object with only a 'body' property, additionalProperties true, and no required fields. Schema coverage is 0%, so the description must compensate. It mentions 'Jellyfin username and password' but does not specify expected parameter names, types, or structure. This is insufficient for an agent to reliably construct a request.

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 ('Sign in') and the resource ('using a Jellyfin username and password'), giving a specific verb and resource. However, it does not distinguish from sibling login tools like seerr_login_plex or seerr_login_local, so it lacks full differentiation.

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 other authentication methods (e.g., Plex login, local login, Jellyfin quickconnect). The description simply states what the tool does, not the conditions that call for its use.

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