search_and_add_show

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

Without annotations, the description adds key behavioral context about auto_add triggering only on single result. However, it omits details on permissions, side effects of adding, and error handling (e.g., multiple results, no results).

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 concise and well-structured, with a front-loaded purpose sentence, followed by clear Args and Returns sections. Every sentence is necessary and no 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 covers basic functionality and parameter semantics adequately, but lacks context on authentication/configuration requirements for Sonarr, detailed output format, and edge-case behaviors. Given the presence of an output schema, the Returns line is minimally sufficient.

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 adds substantial meaning beyond the input schema, which has 0% description coverage. It explains the 'description' parameter with an example and clarifies the conditional behavior of 'auto_add' (only adds when single result found).

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 dual function: search for TV shows by natural language and optionally add to Sonarr. It effectively distinguishes from sibling tools like search_movies and add_show_by_tvdb_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 usage when you have a natural language description, but does not explicitly contrast with alternatives like add_show_by_tvdb_id. It provides a guideline for auto_add but lacks when-not-to-use guidance.

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