item_set_property

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, prerequisites, track type compatibility (audio vs video), or behavior when the property does not exist. This is a minimal, opaque description for a mutation tool.

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, front-loaded sentence with no redundancy. It communicates the core action immediately and efficiently, making it concise and appropriately sized for a simple setter tool.

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?

Despite having an output schema and a well-documented input schema, the description omits critical context: when to use this generic setter vs. dedicated item_set_* tools, acceptable property keys, and audio/video track handling beyond default. This leaves the agent potentially selecting the wrong tool or misusing it.

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?

The schema covers 100% of parameters with explicit descriptions for key, value, item_name, track_type, and track_index. The description adds no extra semantic value beyond the schema, but since schema coverage is complete, a baseline of 3 is appropriate.

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') and the target resource ('a single property on a timeline item'), which is specific and understandable. However, it does not explicitly differentiate itself from sibling setters like item_set_transform or item_set_color, though the generic 'property' wording implies broader applicability.

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 guidance on when to use this tool versus alternatives such as item_set_transform or item_set_crop. The description does not state whether this is for arbitrary properties, fallback for uncovered properties, or how it compares to dedicated setters.

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