set_effect_property

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

Annotations indicate destructiveHint=false (non-destructive) and readOnlyHint=false (modifies). The description adds no additional behavioral context, such as whether setting a property overrides previous values or if there are permissions required. With annotations present, a 2 is appropriate as the description adds minimal value beyond the schema.

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 concise sentence (11 words). It is front-loaded with the verb and resource, but could be more informative without becoming verbose.

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 4 required parameters and no output schema, the description is too sparse. It lacks information about acceptable value ranges, side effects, or return behavior, leaving the agent underinformed about how to use 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 description coverage is 100%, with each parameter having a clear description. The tool description does not add extra meaning beyond what is already in the schema, so baseline 3 is correct.

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 it sets a specific effect property on a clip, using a specific verb ('Set') and resource ('effect property'). It differentiates from sibling tools like 'apply_effect' (adds an effect) and 'get_effect_properties' (reads properties).

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 on when to use this tool versus alternatives. For example, it doesn't mention that this modifies an existing effect property, whereas 'apply_effect' adds a new effect. Users are left to infer context from the name.

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