rename_bin

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the operation name and does not mention side effects, whether a bin must be selected first, what happens to child items, or what the return value indicates.

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 and contains no fluff beyond the phrase 'expanded operation'. However, the meaningful content is not well front-loaded, and the sentence essentially repeats the tool name without adding useful structure.

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?

With no annotations, no output schema, and no parameter descriptions, this one-liner is insufficient for confident invocation. An agent is not told how the target bin is determined, whether it operates on a selection, what constraints exist, or how success is communicated.

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 named parameters, so the baseline is 4. The description adds no parameter guidance, but there are no schema parameters to clarify. The open 'additionalProperties: true' is slightly concerning, yet with no required parameters the description is still minimally adequate.

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 clear verb and resource: 'rename bin'. This distinguishes it from sibling tools like rename_track, rename_clip, and rename_project_item. However, the phrase 'expanded operation' is vague and adds little meaning.

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 provided about when to use this tool versus alternatives such as rename_project_item, rename_clip, or move_items_to_bin. There are no preconditions, no exclusions, and no context for when this tool is the appropriate choice.

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