set_poster_frame

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

With no annotations provided, the description carries full responsibility for disclosing side effects, expectations, or state changes. It merely states the action with no elaboration on consequences, required resources, or whether the operation is reversible. This is a significant gap.

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 extremely short, but this is not conciseness—it is under-specification. It front-loads the core action but offers no additional value. Every sentence is present, but the description fails to convey essential information, making it ineffective despite its brevity.

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 Premiere Pro operation, this description is grossly inadequate. With no annotations, no output schema, and no parameter documentation, the agent has almost no information about how to invoke the tool correctly, what inputs it requires, or what result to expect. The level of completeness is far below a minimum viable description.

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 input schema defines no explicit parameters (only allows arbitrary properties), and the description does not mention or clarify what inputs the operation expects. Even though the schema has zero defined parameters, the tool likely requires context (e.g., a target clip), and the description fails to compensate for this ambiguity.

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 it sets a poster frame in Premiere Pro, but provides no detail on what a poster frame is, what object it applies to (clip, sequence, etc.), or how the operation behaves. This is only slightly more informative than the tool name, lacking the specificity needed to distinguish it from similar operations.

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 versus alternative approaches. No mention of prerequisites, contexts, or exclusions. The description provides zero usage direction, leaving the agent to guess.

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