search_media

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

With no annotations, the description carries the full burden and does well by disclosing that it searches TMDB rather than Plex, and that it returns TMDB IDs needed for requests. It also lists return fields including availability status, adding useful behavioral context beyond a simple search.

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-structured: purpose, key distinction, usage context, parameters, and return format. Every sentence serves a purpose with no fluff or repetition.

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 tool's moderate complexity and no annotations, the description sufficiently covers what the tool does, when to use it, and what it returns. The presence of an output schema reduces the need to detail return values, and the description aligns well with that.

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 0%, but the description compensates with an Args section explaining 'query' as the search term and 'media_type' as an optional filter with allowable values 'movie' or 'tv'. This adds meaning beyond the raw schema, though it could be slightly more detailed about the query's matching behavior.

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?

States a specific verb and resource: 'Search for movies and TV shows in Overseerr' with a clear scope (TMDB external database) and return value (TMDB IDs). Explicitly distinguishes itself from the sibling tool search_library, which is a strong differentiator.

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?

Gives direct usage context: 'Use this to find media by title before making a request.' It also provides an explicit alternative: 'To search content you already own, use search_library instead.' This clearly tells the agent when to choose this tool over a sibling.

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