search_plex_library

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

With no annotations present, the description carries the full burden. It discloses that the results table shown to the user exactly matches the return, the default limit is small, and that pagination may require follow-up calls—context beyond the schema. It doesn't mention authentication or rate limits, but those may be less critical; still, it adds valuable operational behavior.

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 well-organized with front-loaded purpose and usage, followed by practical tips. It uses clear examples and covers edge cases (default limit, pagination) without unnecessary fluff. Every sentence earns its place.

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 search tool with 7 optional params and no output schema, the description is remarkably complete. It explains filtering, combination, limits, pagination, and the exact relation to the displayed results. Everything an agent needs to use it effectively is covered.

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?

Schema coverage is 100%, so each parameter is already documented with descriptions (year, actor, genre, limit, title, offset, library). The description reinforces filter combination and library semantics (e.g., '4k') but doesn't add much beyond schema. Baseline 3 is appropriate.

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 searches the user's actual Plex library by multiple filters (genre, actor, title, year, library) and explicitly differentiates it from sibling tools like check_movie_status. It specifies what it answers ('what the user owns or can watch'), making its purpose unambiguous.

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?

It gives explicit when-to-use guidance ('Use this to answer what the user owns or can watch') and when-not-to-use ('use check_movie_status for Radarr/download status'), naming the alternative. It also provides detailed operational instructions on how to express user requests as filters and how to handle pagination with limit and offset.

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