set_effect_property

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

Annotations already indicate this is a mutating operation, so the description adds little behavioral context. It does not disclose side effects, whether values are applied live, what happens when an effect/property does not exist, or any other relevant behavior.

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, clear, front-loaded sentence with no filler. It is concise, though very sparse, and could incorporate a pointer to related tools or sourcing requirements.

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 mutating tool this is thin. It does not mention how to discover valid effect/property names, whether to call get_effect_properties first, what the result is if the value is invalid, or which sibling tools are alternatives. The sparse description leaves the agent without vital context for correct 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?

All four parameters are described in the input schema, so the description carries no additional burden. It does not add meaning beyond the schema, but the schema already provides adequate detail.

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 a specific action ('Set the value') on a specific resource ('effect property on a clip'). It is distinguishable from generic setters, though it does not explicitly differentiate from similar sibling tools like set_effect_values or copy_effect_values.

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 provides no guidance on when to use this tool, when not to use it, or how to obtain valid effect_name and property_name values. It leaves the agent to infer the use case from the name.

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