pr_export

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

With readOnlyHint=false already covering mutability, the description adds genuinely new behavior: the default path enqueues into Adobe Media Encoder and starts a batch, while direct:true blocks inside Premiere. That blocking/non-blocking distinction is exactly the kind of trait an agent needs and cannot infer from annotations.

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?

Front-loads purpose then packs mode, range, and default preset into a single dense line with no filler. The telegraphic 'range entire|inToOut|workArea' phrasing is efficient, though slightly clipped at the cost of readability.

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 7-param mutation tool with no output schema and low schema coverage, the description omits what is returned (queue job vs written file), whether the default AME path waits for completion, and how presetName and presetPath interact. The mode and range semantics it does cover are the most important ones.

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 coverage is only 14%, but the description compensates for the key ones: it defines direct, enumerates the range values, and implies startQueue semantics ('default, starts batch'), plus pins the default preset name. It does not explain the required outputPath, nor the precedence/relationship between presetName and presetPath.

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 (export) and resource (a Premiere Pro sequence) plus the preset mechanism (.epr). It clearly separates itself from adjacent siblings like pr_exportFrame and pr_exportProjectFile, which export a frame or a project file, not a rendered sequence.

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?

Explains the two execution modes and which is the default (AME queue, starts batch) versus the opt-in blocking mode (direct:true). It gives enough context to select a mode, but names no alternatives or when-not-to-use cases.

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