jellyfin_set_overview

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

Without annotations, the description must disclose behavior. It explains the lock mechanism (prevents overwrite on refresh), the confirm parameter (preview vs write), and the scope (collections/movies by name/id). This goes beyond the schema's defaults. However, it omits details like return values or error handling, which may be covered by the output schema.

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 four sentences, each earning its place: purpose, lock behavior, confirm behavior. It is front-loaded with the core action. 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 that an output schema exists (context says true) and no annotations, the description covers the main behavior but lacks details on edge cases (e.g., item not found, distinguishing name vs ID). It does not specify if it works on other item types beyond movies and collections, which would be important.

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 clarify all parameters. It explains lock (default true, adds to LockedFields), confirm (false previews, true writes), and overview (the text to set). Item_ref is implied as 'by name or id', but not detailed. This adds meaning beyond the bare schema.

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: 'Set an item's Overview/description'. It specifies the resource type ('a collection or a movie') and how to identify it ('by name or id'). This uniquely distinguishes it from sibling tools like jellyfin_list_movies or jellyfin_create_collection.

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 provides no guidance on when to use this tool compared to alternatives. It does not mention when not to use it or suggest other tools for related tasks. The only usage context is about lock and confirm behavior, not about selection between tools.

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