create_bin

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the action and purpose but does not disclose side effects (e.g., whether the bin is created at the root or requires a parent), error conditions, or any constraints. For a creation tool, 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 a single, concise sentence that is front-loaded with the action and purpose. It contains no fluff, but it could be slightly more informative without becoming verbose. It earns its place but doesn't go beyond the minimum.

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 tool's simplicity (2 params, no output schema), the description is somewhat adequate, but it lacks context about the parent bin behavior, default location, or any prerequisites. With no annotations and no output schema, the description should provide more behavioral context to be 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 description coverage is 100%, so the schema already documents both parameters (name and parentBinName). The description adds minimal value beyond the schema, only implying the bin is created in the project panel. The baseline of 3 is appropriate since the schema handles parameter documentation.

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 tool creates a new bin (folder) in the project panel to organize media. It uses a specific verb ('creates') and resource ('bin'), and the parenthetical clarifies the domain. It doesn't explicitly distinguish from sibling tools like create_smart_bin or delete_bin, but the action is distinct enough.

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 usage context (organizing media in the project panel) but does not explicitly state when to use this tool versus alternatives like create_smart_bin or import_folder. No exclusions or alternative tool mentions are provided, so the guidance is implied rather than explicit.

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