tdarr_add_audio_codec_exclude

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 describes a mutation (adding a codec) but fails to disclose side effects (e.g., overwriting existing entries, idempotency, permission requirements). The description lacks behavioral context.

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 sentence, which is concise, but the ambiguous 'excluded/included' detracts from clarity. It could be restructured to be more precise.

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 operation with 2 parameters and no output schema, the description omits necessary context such as the role of this setting in the broader transcoding workflow and expected behavior after addition.

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 descriptions for both parameters (100% coverage), but the tool description adds no extra meaning. It does not clarify the expected format for 'ele' (e.g., codec name like 'aac') or the source of 'dbID'.

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 identifies the action ('Add') and the resource ('an audio codec'), but the phrase 'excluded/included' introduces ambiguity about whether the operation adds to an exclusion or inclusion list, especially given the tool name specifies 'exclude'.

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?

No guidance on when to use this tool versus siblings like tdarr_remove_audio_codec_exclude or tdarr_update_audio_codec_exclude. The description does not explain what 'basic audio transcoding settings' are or when this addition is appropriate.

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