ae_timeRemap

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

Annotations already declare this is a non-readonly, non-destructive, closed-world mutation, and the description adds that it enables time remapping specifically on footage/precomp layers. It does not disclose whether existing remap keys are replaced or appended, nor any error behavior for unsupported layer types.

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?

A single dense sentence that front-loads the operation before listing modalities and the alternate freezeAt path. It is appropriately sized, though slightly packed with parenthetical examples.

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 5-parameter mutation with no output schema and partial schema coverage, the description covers the primary path but leaves 'extendTo' semantics and key-overwrite behavior unaddressed. An agent could call it correctly for common cases but may misuse edge parameters.

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?

With 40% schema coverage, the description must compensate. It does add meaning for 'keys' as remap pairs and for 'freezeAt' as a single-time freeze, but 'extendTo' is left entirely unexplained in both schema and description.

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?

States a specific verb and resource: enable time remapping on a footage/precomp layer and set remap keys. It is clear this differs from ae_timeStretch and ae_trimLayer, though no sibling is named explicitly for 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?

The parenthetical 'freeze frames, speed ramps' and 'freezeAt a single time' imply when this tool is appropriate, giving useful scenario context. However, it never states when to prefer ae_timeStretch or ae_trimLayer instead, leaving the agent to infer the boundary.

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