radarr_trigger_search

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

With no annotations, the description must fully disclose behavior. It implies a mutation (triggering a search) but omits important details: whether the search is synchronous or asynchronous, if it modifies state, any permissions needed, or rate limits. The description is too minimal for a trigger action.

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 a single sentence of 13 words with no unnecessary text. It front-loads the core purpose ('Trigger a search for missing movies') and immediately presents the optional filter. Perfectly concise.

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 simple one-parameter tool, the description is adequate but incomplete. It does not explain the result of the search, whether it's immediate or queued, or any side effects. Given the absence of annotations, more behavioral context would be expected for full completeness.

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 sole parameter 'movieId' is already well-documented in the schema (100% coverage), stating it can be omitted to search all missing. The tool description adds no extra meaning beyond the schema, so the baseline score of 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 identifies the tool's action ('trigger a search') and resource ('missing movies'), with an optional filter ('for a specific movie'). However, it does not explicitly distinguish from sibling tools like 'radarr_search' or 'sonarr_trigger_search', which could cause confusion.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, when to include a movieId, or when not to use it. The description only states that the parameter is optional, without explaining trade-offs.

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