rename_bin

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether the operation mutates the project, requires a selected bin, or returns any confirmation. This is a significant gap for a write operation.

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 sentence and is concise in length, but it is severely under-specified. It does not earn its place because it omits vital information about selection context and side effects.

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?

Given the simplicity of the tool name, the description is grossly inadequate. There is no output schema, no annotations, and no explanation of prerequisites or consequences. It cannot guide an agent to invoke the tool correctly.

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 parameters, so the description must clarify how the bin is identified (e.g., via current selection). It does not provide any such information, leaving the operation ambiguous. The baseline for zero parameters is 4, but the description fails to add necessary clarification.

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 clearly states the operation is to rename a bin, which is a specific resource in Premiere Pro. However, it lacks specificity about which bin is targeted (e.g., the selected bin) and does not differentiate from similar sibling tools like rename_project_item or rename_clip.

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 alternatives such as rename_project_item or rename_clip. The description merely states 'Premiere Pro expanded operation: rename bin' without any context on prerequisites or suitable situations.

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