Preview After Effects Render Handoff

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningful context by stating it reads both connected hosts and binds approval to file metadata and project/bin identity. It also reinforces safety by listing operations it does not perform, going beyond what annotations provide.

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 two sentences with no filler. The first sentence states the primary purpose, and the second provides behavioral scope and exclusions. Every clause earns its place and the description is easy to parse quickly.

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?

The description is sufficient for a preview tool with strong annotations, a complete schema, and an output schema. It explains the core behavior and important exclusions, though it could be slightly more explicit about the relationship to apply_after_effects_render_handoff and the prerequisite that both hosts must be connected.

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 all six parameters in detail. The description does not add parameter-specific meaning beyond the schema, but it does support the overall context by mentioning 'single-file render' and 'existing bin'. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 specific action ('Preview import'), the resource ('one completed After Effects single-file render'), and the destination ('an existing Premiere bin'). It also explicitly lists what the tool does not do, making it easy to distinguish from apply_after_effects_render_handoff and other AE-related tools.

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 description gives clear context that this is a preview-only operation and explicitly excludes render, import, and timeline editing. However, it does not name the alternative apply_after_effects_render_handoff or state that this should be used before applying the handoff, leaving some inference to the agent.

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