exportWithAME

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

No annotations exist, so the description carries the full disclosure burden. It does convey that work is queued in an external app and that rendering does not start unless renderImmediately is set, but it omits whether the call blocks, whether it returns a job/render identifier, what happens when AME is unavailable, and whether an existing file at outputPath is overwritten.

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?

One sentence, front-loaded with the action and target, with zero filler and no repetition of the tool name.

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 schema is fully described and there is no output schema to explain, but for a tool that hands work to an external application the description should at least mention the AME dependency and what the agent gets back. Without those, an agent cannot plan around the call's asynchronous nature.

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 each of the three parameters is already documented in the schema, including the default-to-active-comp behavior and the renderImmediately default. The description adds no syntax, format, or constraint detail beyond that, which is the baseline case.

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?

Names a specific verb (send) and resource (composition) plus the destination system (Adobe Media Encoder render queue), and 'high-quality background rendering' implicitly separates it from preview exports. It stops short of naming the sibling it displaces (exportPreviewVideo / exportFrame), so the boundary is inferred rather than stated.

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?

Usage is only implied: 'high-quality' and 'background rendering' suggest a final-quality render rather than a quick preview, which lets an agent guess it should prefer exportPreviewVideo for fast checks. No explicit when-to-use or when-not-to-use guidance, and no prerequisites such as AME needing to be installed or running.

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