Premiere project

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

Annotations already declare destructiveHint=true, but the description adds nothing beyond that. It does not disclose what gets destroyed, any side effects, required permissions, or error behavior. Since annotations cover only the single destructive flag, the description carries a heavy burden and fails to provide any additional behavioral context. No contradiction exists, but there is zero added value.

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 a single short sentence, which is concise in length, but that brevity comes at the cost of clarity. It is under-specified rather than efficiently packed with information, so it does not earn its place by adding value.

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 tool with 6 parameters, nested objects, a destructive hint, and no output schema, the description is completely inadequate. It provides no overview, no parameter guidance, no usage scenarios, and no expectations about return values or side effects. An agent cannot safely or correctly invoke this tool based on the given definition.

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 0%, so the description must explain the 6 parameters (actionId, args, target, approvalId, operationId, expectedRevision) but does not mention any of them. An agent has no idea what values to provide, what the object types for args and target mean, or the purpose of the IDs and revision fields. This is a severe gap.

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 states a verb ('run') and a resource ('typed project lifecycle action'), but 'typed' is undefined and no specifics are given about what actions are available or what a lifecycle includes. It does not help distinguish this from siblings like premiere_operations or premiere_api, so an agent cannot tell what this tool uniquely does.

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?

There is no guidance on when to use this tool, when not to use it, or any mention of alternative tools. The description gives no context for selecting it over the many premiere_* siblings, so the agent is left without decision support.

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