create_bin

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

With no annotations, the description carries the full burden of behavioral disclosure. It clarifies that a bin is a folder in the project panel and adds the context 'to organize media', but it does not mention potential side effects, permission requirements, or failure conditions, leaving these aspects implicit.

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 (12 words) that states the core function and context with no redundant phrasing. It is front-loaded and every word earns its place.

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 simple create operation with full schema coverage and no output schema, the description is adequate and unambiguous. However, it could further clarify that parentBinName is optional or explain what happens when no parent is specified, which would make it more complete.

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 coverage is 100%, with both 'name' and 'parentBinName' documented in the schema. The description adds no parameter-specific details beyond what the schema already provides, so it meets the baseline but does not enhance understanding.

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 uses a specific verb 'creates' and identifies the resource as a 'new bin (folder)' in the 'project panel', clearly distinguishing it from sibling tools like delete_bin, rename_bin, and create_smart_bin. It also indicates the purpose ('to organize media').

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?

The description implies the tool is for organizing media in the project panel but does not explicitly state when to use it over alternatives like create_smart_bin or delete_bin. There is no when-not guidance or alternative tool references.

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