jellyfin_collection_items

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

No annotations provided, so the description carries full burden. It discloses that collection_ref accepts a name or ID (including prefix), adding behavioral context beyond a simple parameter type. However, it does not mention rate limits, authentication, or return format (though output schema exists).

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?

Two concise sentences, front-loaded with the main action and immediately followed by parameter clarification. 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?

Given the low complexity (one parameter, no enums, output schema present), the description is complete. It explains the tool's purpose and parameter semantics adequately for an AI agent to use it correctly.

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 sole parameter has zero schema description coverage, but the description adds substantial meaning: 'collection_ref accepts a collection name or a Jellyfin id (or its unique prefix)'. This fully compensates for the lack of schema-level documentation.

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 ('List the movies inside a collection') and specifies the input flexibility ('by collection name or id'), distinguishing it from sibling tools like jellyfin_list_movies and jellyfin_list_collections.

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 collection reference, but does not explicitly state when to use this tool versus alternatives (e.g., jellyfin_list_movies or jellyfin_list_collections) or provide exclusions.

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