radarr_get_rename

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

The annotation readOnlyHint=true aligns with the 'List' verb, but the description adds no behavioral context such as pagination, result format, or any special behavior. It does not contradict the annotation but provides no additional transparency.

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 very short and front-loaded, but it is under-specified rather than efficiently concise. It reads as two fragments and lacks enough substance to be considered well-structured.

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 tool's purpose remains ambiguous and the single parameter is unexplained. The description is insufficient for an agent to decide when to invoke this tool or how to correctly use the movie_id parameter.

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 only repeats the parameter name 'movie_id' without explaining its purpose or effect. With 0% schema description coverage, the description fails to compensate and gives the agent no meaningful understanding of the parameter.

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 'List rename' gives a verb and a vague resource, but 'rename' is not defined—could be rename history, rename tasks, or something else. It does not clarify what specific rename-related data is being listed and does not distinguish from sibling tools.

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. The description merely says 'Query params: movie_id,' which offers no context about the intended use case or when this listing is appropriate.

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