encode_project_item

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 say whether encoding is synchronous, whether files are written, whether it operates on the selected item, or whether it requires a specific project state.

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 terse, but 'Premiere Pro expanded operation' is filler and the remainder merely restates the tool name. It is under-specification rather than carefully structured conciseness.

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 no-parameter operation, an agent still needs to know what state is required (e.g., a selected project item), what side effects occur, and what result to expect. There is no output schema and no behavioral description to fill these gaps.

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 schema has zero documented parameters, so there is no parameter detail the description must add. The no-parameter baseline of 4 applies; the loose additionalProperties:true is not documented as supported input.

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 supplies a verb and a resource ('encode project item'), so an agent can infer the broad purpose. However, 'expanded operation' is opaque, and the description does not distinguish this from sibling tools like encode_file or start_batch_encode.

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?

No guidance is given about when to use this tool rather than encode_file, start_batch_encode, export_sequence, or add_to_render_queue. The phrase 'expanded operation' provides no practical selection context.

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