set_transcode_on_ingest

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this enables or disables transcoding, whether it affects existing media or only future ingests, whether it is project-wide or per-item, or what side effects it may have. The behavior is entirely opaque.

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 short, but the phrase 'Premiere Pro expanded operation' is filler that does not earn its place, and the remainder merely repeats the tool name. There is no useful front-loaded information beyond what is already visible in the 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?

For a zero-parameter operation with no output schema, the description should still clarify what setting is being modified and what the operational effect is. The current text is too thin for an agent to know whether calling this tool will change project settings, trigger re-ingesting, or require additional context.

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?

The tool has zero documented parameters and no required parameters, so the schema has no parameter semantics to cover. The baseline for zero-parameter tools is 4, and the description need not compensate for missing parameter descriptions.

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 'set transcode on ingest' is a direct restatement of the tool name with underscores replaced by spaces. It adds no new information about what the operation does or what object it affects, and the 'Premiere Pro expanded operation' prefix is boilerplate.

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 no guidance on when this tool should be used, what condition warrants it, or how it compares to related operations such as encode_project_item, refresh_media, or set_footage_interpretation. There are no exclusions or alternatives mentioned.

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