set_clip_property

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the operation is a direct mutation ('set...directly') but says nothing about required permissions, side effects, validation failure, whether existing values are overwritten, or how invalid or unsupported property names are handled.

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?

Two short sentences with no filler. The core action is front-loaded, and the sibling preference is stated immediately after. Every word earns its place.

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 an arbitrary low-level property setter with no parameter descriptions and no annotation context, the description is too thin: it lacks examples, a pointer to where property names are documented, value-type guidance, and error behavior. The output schema helps with return values, but the input semantics remain under-specified.

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 0%, so the description must compensate, but it only clarifies that property_name refers to a documented timeline item property. It does not explain the expected shape or type of value, how item_id should be obtained, or any constraints on property 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 identifies the action ('set'), the resource ('Resolve timeline item property'), and the scope ('any documented'), and it names the main sibling alternative in the second sentence. An agent can distinguish this low-level setter from focused tools like set_clip_transform, set_clip_enabled, or set_clip_grade.

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 instruction 'Prefer set_clip_transform for common changes' gives explicit routing guidance for a key alternative, implying this tool is for less common or direct property writes. It does not enumerate all sibling exclusions, but for a generic low-level setter this is adequate context.

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