add_show_by_tvdb_id

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

No annotations are provided, so the description carries full burden. It states it adds a show but does not disclose side effects, permissions, duplicate handling, or error scenarios. The return is vaguely described as 'Result of the add operation' despite an output schema existing. More behavioral context is needed.

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 Args and Returns sections. Every sentence is informative without redundancy. It is appropriately sized for the tool's complexity.

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 presence of an output schema (though not shown), the description need not detail return values. However, it lacks context about prerequisites (e.g., Sonarr configuration, authentication) and error conditions. It is adequate but not fully complete for a tool with no annotations.

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 schema description coverage at 0%, the description adds significant meaning: explains 'tvdb_id' as 'The TV Database ID', 'title' as 'The title of the show', and 'root_folder' as 'Optional root folder path' with an example. This compensates for the schema's lack of descriptions.

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 'Add a specific TV show to Sonarr using its TVDB ID,' specifying the verb 'add', the resource 'TV show', and the method 'using TVDB ID'. It distinguishes itself from siblings like 'add_movie_by_id' and 'search_and_add_show' by focusing on direct addition via 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 a TVDB ID is available, but does not explicitly state when not to use this tool or mention alternatives like 'search_and_add_show' for cases where the ID is unknown. No direct guidance on prerequisites or exclusions.

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