sonarr_lookup_series

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

No annotations are provided, so the description carries the full burden. It explicitly states the tool searches and returns a tvdbId, implying a read-only lookup. However, it does not mention potential behavior like handling multiple matches or case sensitivity, but for a simple search tool, this is adequate.

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 two sentences, direct and front-loaded with the purpose and return value. Every sentence provides critical information without any fluff.

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?

The description is complete for a simple lookup tool. It explains what it does, what it returns, and how it integrates with sonarr_add_series. An output schema exists (not shown), so no need to detail return format.

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 provides no description for the 'term' parameter (0% coverage). The description clarifies that 'term' refers to the series title, which adds essential meaning beyond the schema's bare type definition.

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 it searches for series by title, specifically for adding a new series. It also explicitly mentions that it returns the tvdbId needed for sonarr_add_series, distinguishing it from sibling tools like sonarr_list_series or sonarr_search_season.

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 indicates when to use this tool: when adding a new series and needing the tvdbId. It does not explicitly mention when not to use, but the context of siblings and the tool's purpose provides sufficient guidance.

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