set_work_area

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

No annotations are provided, so the description must disclose behavioral traits. 'Set the work area' implies a mutation (changing something), but the description does not reveal if it overwrites previous settings, requires an existing composition, or has side effects like resizing other components. The description is too vague to help the agent anticipate consequences.

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 very short (one sentence), which makes it easy to read quickly. However, it sacrifices necessary detail for brevity, bordering on under-specification. It earns its place but could benefit from an extra sentence or two to cover usage and semantics without losing conciseness.

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 complexity (4 params, no output schema, many sibling tools), the description is incomplete. It does not explain what 'set the work area' means operationally, how the parameters relate to each other, or what the tool returns (if anything). With no output schema, at minimum the description should state the expected outcome or return value.

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 50%, with 'start' and 'duration' having descriptions. The description adds no additional meaning beyond these param descriptions; it does not even list them or explain how they interact. For the undocumented params (compId, compName), the description provides zero help, and the schema descriptions are minimal (just type names and units). The description could have clarified the role of compId vs compName.

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 states the verb 'set' and resource 'work area of a composition,' which is clear enough to understand the basic action. However, it lacks specificity about what 'work area' means in context (e.g., does it set the composition's work area for rendering or editing? It does not distinguish from sibling tools like get_composition_info or modify_composition, which deal with composition settings.

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. With many composition-related siblings like modify_composition, get_composition_info, and list_compositions, the description does not clarify whether this tool is for setting the preview region, render range, or something else entirely, nor does it mention any prerequisites or common use cases.

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