set_effect_property

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

No annotations are present, so the description carries full burden for behavioral traits. It does not disclose any side effects (e.g., overwriting, keyframe creation), prerequisites (effect must exist), or error scenarios (property not found). Minimal transparency.

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, well-formed sentence with no fluff. It could be improved by adding more detail (e.g., return value) while staying concise, but as is it is efficient.

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 the tool modifies state and has 4 parameters with no output schema or annotations, the description is too brief. It lacks expected information on return behavior, error cases, or success indicators, making it incomplete for a mutation tool.

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 descriptions for all 4 parameters. The description adds no extra meaning beyond what schema provides, so baseline 3 is appropriate. It does not clarify value range or units, but schema already covers names.

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 action (Set), object (value of effect property), and subject (clip). It distinguishes from sibling tools like 'apply_effect' or 'get_effect_properties' by specifying 'effect property' setting. However, it could be more specific about the context (e.g., timeline clip) to reach a 5.

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 versus alternatives (e.g., 'set_clip_opacity' for direct properties) or when not to use it. There are no prerequisites or context hints, leaving the agent without decision support.

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