sonarr_get_episode

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

The readOnlyHint annotation already declares this is a safe read operation, and the description adds no behavioral context beyond that. It does not disclose return format, error behavior, or any special constraints; the term 'by id' merely restates the schema parameter.

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?

One short sentence with no filler, front-loads the verb and resource. The grammatical typo does not affect conciseness.

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 get-by-id tool with an output schema and readOnlyHint annotation, the description is mostly sufficient. It could mention that the id is the Sonarr episode ID or point to sonarr_list_episode for enumeration, but these are minor gaps given the tool's simplicity.

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?

With 0% schema description coverage, the description's 'by id' does clarify that the integer 'id' parameter identifies the episode to fetch, adding some meaning beyond the bare schema. However, it does not explain where the id comes from or its format, so the compensation is minimal.

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 uses the specific verb 'Fetch' and identifies the resource ('a single episodes by id'), clearly distinguishing this from sibling list/monitor/update tools. Despite minor grammatical issue ('episodes' vs 'episode'), the intent is unambiguous.

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 phrase 'by id' implies this tool is for retrieving one specific episode when its ID is known, but it does not explicitly state when to prefer this over sibling tools like sonarr_list_episode or sonarr_get_episodefile. No alternatives or exclusions are mentioned.

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