tdarr_add_video_codec_exclude

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

No annotations are provided, so the description must disclose behavior. It only states the action but does not explain side effects, persistence, required permissions, or impact on existing settings. The agent cannot infer whether this modifies a config file, updates a database, or triggers a re-scan.

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 of 11 words, front-loaded with the verb. It is concise, but the inclusion of 'excluded/included' adds ambiguity that could have been avoided with a few more words.

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 no output schema and lack of annotations, the description should provide more context. It fails to explain how this tool fits into the workflow of video codec management, leaving the agent without enough information to decide between add, remove, or update siblings.

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?

Schema coverage is 100% with both parameters having descriptions. The description adds no new semantic details beyond the schema—e.g., it doesn't specify the expected format for ele (like codec names) or how to obtain dbID. Baseline is 3, and no extra value is provided.

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 verb 'Add' and the resource 'video codec to be excluded/included in basic video transcoding settings'. It distinguishes from siblings like tdarr_remove_video_codec_exclude and tdarr_add_audio_codec_exclude, but the phrase 'excluded/included' is ambiguous—it's unclear whether it adds to an exclusion or inclusion list.

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 is provided on when to use this tool vs alternatives like tdarr_remove_video_codec_exclude or tdarr_update_video_codec_exclude. The description does not mention prerequisites, context, or typical use cases.

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