radarr_get_credit

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

The readOnlyHint annotation already covers the safe read-only nature. The description adds minimal behavioral context beyond the resource type (movie credits), and does not discuss response details or error behavior. It does not contradict the annotation.

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 concise sentence, front-loaded with the verb 'Fetch', and contains no extraneous words. It is appropriately sized for such a simple tool.

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 low complexity, output schema, and annotations, the description is mostly adequate. The main gap is the ambiguity around whether 'id' refers to the credit id or a movie id, which could confuse an agent. This is a notable but not critical omission.

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 schema has one required 'id' with no description (0% coverage). The description only says 'by id', which just restates the parameter name and does not clarify whether it is a credit id or a movie id, nor any additional constraints. This is insufficient to compensate for the lack of schema documentation.

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 tool fetches a single movie credit (cast/crew) by id, using the specific verb 'Fetch'. This distinguishes it from sibling radarr_list_credit, which lists credits, by emphasizing 'single' and 'by id'.

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?

The description implies the tool is for retrieving a specific credit when its id is known, but it does not explicitly contrast with list_credit or state when not to use it. The get-by-id pattern is implicit but not clearly articulated.

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