remove_audio

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Remove audio' implies a mutating operation, but it does not explain whether the input file is modified, whether a new file is produced, whether audio removal is destructive, or what the output looks like.

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 with no wasted words and the core action is front-loaded. It is concise, though it sacrifices informative detail that other dimensions require.

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?

Despite having only one parameter, the tool lacks sufficient context about output behavior, side effects, and how to specify the input. The schema and output schema offer no additional information, so the description is incomplete for trustworthy invocation.

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?

There is a single required parameter, input_video, and the schema provides no description. The tool description also does not explain what format input_video should take, such as a file path, URL, or uploaded asset, leaving the agent to guess.

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 uses a clear verb and resource: 'Remove audio from a video.' It is specific enough to distinguish from most sibling tools, though it does not explicitly contrast with extract_audio or replace_audio.

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 about when to use remove_audio versus alternatives like extract_audio, replace_audio, or fade_audio. The description gives no context for choosing this tool over its siblings.

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