search_media

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the 'Plex libraries' scope but does not mention pagination behavior, match semantics, or what happens when no results are found, adding minimal value beyond the annotations.

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 only one sentence, which is concise, but it is under-specified rather than efficiently compact. It omits critical usage and behavioral details, making it too minimal to earn a higher score for structure.

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?

With no output schema, the description should clarify return format or result behavior but does neither. It also fails to position the tool relative to its many search-related siblings, leaving an incomplete picture for a tool with five parameters.

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 description coverage is 100% with descriptive text for all five parameters, including defaults and enum values. The description itself adds no parameter-specific information, so the baseline score of 3 is appropriate due to the schema's completeness.

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 (search) and resource (media in Plex libraries), making the basic purpose understandable. However, it does not differentiate from sibling search tools like radarr_search or sonarr_search, nor does it clarify whether it searches across all libraries or only within a specific library.

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 alternatives such as radarr_search, sonarr_search, or get_library_items. There are no explicit context clues or exclusions to help an agent choose correctly among the many sibling tools.

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