radarr_search_releases

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

The description explicitly flags 'WRITE: this modifies your Radarr instance', which adds a clear behavioral warning beyond the annotations (readOnlyHint: false). It conveys that this is not a read-only operation, though it does not detail what exactly gets modified or any side effects.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence adds the write warning. It is efficient, though it could include more details without becoming bloated.

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?

Despite having an output schema, the open-ended 'body' parameter leaves significant ambiguity. The description does not explain the expected structure beyond movieId, nor does it mention how search behavior is scoped (e.g., available options). This is insufficient for a parameter that accepts arbitrary properties.

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 input schema is a single open object with no descriptions (0% coverage). The description mentions 'movieId and other options', which gives a hint but does not enumerate valid properties, defaults, or nested structure. This is minimal compensation for the undocumented schema.

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 for releases for a movie', which is a specific verb and resource. It also identifies the key parameter in the body (movieId), distinguishing this from other release-related tools like list or push releases.

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_list_release or radarr_push_release. It only specifies that the body carries movieId, but does not compare with sibling tools or indicate prerequisites or contexts where this tool is preferred.

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