overseerr_search_media

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

Annotations are absent, so the description must carry the full burden of behavioral disclosure. It does not state whether the operation is read-only, what the return format is, or any authentication/rate-limit requirements. It only mentions pagination default.

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 concise with a clear one-sentence purpose followed by a structured Args section. Every part serves a purpose, though the Args section is somewhat templated and not fully integrated.

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?

The description covers the tool's purpose and parameters adequately for a simple search tool. However, without an output schema, it should describe the return value (e.g., a list of matching media) and ideally mention usage context relative to other tools.

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 description explicitly explains both parameters: query as the search term with an example, and page as the page number with default 1. This adds significant meaning beyond the bare schema, which has 0% description coverage.

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 'Search for movies and TV shows available on Overseerr' with a specific verb (search) and resource (media on Overseerr). This distinguishes it from sibling tools like overseerr_get_users or overseerr_movie_requests.

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 explicit guidance on when to use this tool versus alternatives such as overseerr_get_available_libraries or overseerr_request_movie_to_library. The need to search before requesting is implied by the sibling names but not stated.

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