set_item_fade_out

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not state whether the operation requires item selection/valid indices, whether it overwrites an existing fade, whether length is clamped to the item duration, or whether it is undoable. Only the units of one parameter are given.

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?

Very short and front-loaded, with the core action in the first sentence. The 'Args:' block is minimal, though it wastes a line documenting only one of three parameters.

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 mutation tool with three required, undocumented parameters, zero annotations, and no output schema, this description is far too thin. It omits targeting semantics, unit constraints, and any behavioral or failure context an agent would need to invoke it correctly.

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 0% across three required parameters, and the description only annotates one of them ('length: Fade-out length in seconds'). The two index parameters (track_index, item_index) — the ones an agent is most likely to get wrong — are left completely unexplained.

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?

States a specific verb and resource ('Set the fade-out length of a media item'), which is unambiguous and implicitly distinguished from the sibling set_item_fade_in. It does not, however, note anything about which item is targeted or how that differs from related item-mutation tools.

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?

There is no when-to-use guidance, no alternatives named, and no prerequisites stated. An agent cannot tell from this text whether the target item must first be selected or whether the fade must fit inside the item's length.

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