set_footage_interpretation

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

With no annotations, the description must fully carry behavioral disclosure. 'Sets' correctly implies mutation, but the description does not state whether this changes the interpreted footage persistently, whether projectItemId is authoritative, what happens if both overrides are omitted, or what the agent should expect afterward. This is a meaningful gap 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 that names the action, the settings involved, and the target. There is no filler, repetition, or unnecessary detail, so 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?

Given no annotations and no output schema, the description should provide more behavioral and selection context. It fails to guide the agent away from similar sibling tools, does not explain effects or prerequisites, and leaves the relationship to get_footage_interpretation and the override-specific setters unaddressed.

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%, so the schema already documents each parameter. The description adds only minimal context by grouping frameRate and pixelAspectRatio under 'footage interpretation settings', which is a slight conceptual enhancement but not enough to raise the score above the baseline.

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 uses a specific verb ('Sets') and a concrete resource ('footage interpretation settings') and names the key fields (frame rate, pixel aspect ratio) and scope ('for a project item'). It does not explicitly contrast itself with siblings like set_override_frame_rate or set_override_pixel_aspect_ratio, so it stops short of full sibling differentiation.

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 given on when to use this tool versus alternatives. The description provides no exclusions, no mention of get_footage_interpretation for reading, and no clarification of how this differs from the more targeted override setters among the siblings.

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