seerr_check_jellyfin_quickconnect

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

The readOnlyHint annotation already indicates safe read-only behavior. The description adds minimal context beyond restating the purpose; it does not say what 'authorization status' means or how the secret is used. No contradiction with the annotation.

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, front-loaded with the action and resource. It is efficient, though it could have added needed context without losing conciseness.

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 signature and an output schema, but the description omits the Quick Connect workflow context (e.g., calling after initiate, before authenticate). For an agent to use it correctly, the description should reference the flow or the meaning of the returned status.

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 defines a single required 'secret' string with no description, and the description does not explain what this secret is or where to obtain it. With 0% schema description coverage, the description fails to compensate.

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 uses the verb 'Check' with the resource 'Quick Connect authorization status', clearly indicating a read-only status lookup. It distinguishes from sibling tools like seerr_initiate_jellyfin_quickconnect and seerr_authenticate_jellyfin_quickconnect by specifying 'status'.

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 seerr_initiate_jellyfin_quickconnect or seerr_authenticate_jellyfin_quickconnect. The description does not mention the Quick Connect flow or suggest any alternatives.

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