bitpull_add_model_folder

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

Annotations supply only destructiveHint=false, so the description carries the rest of the burden and does not meet it. It never says whether the folder is created if missing, whether the path must already exist, whether this only records a setting, or what happens on a duplicate path — all material for an "add" operation that changes configuration.

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?

One front-loaded sentence with an inline example and no filler; the verb and resource appear immediately, and the example is embedded rather than given its own sentence.

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 one-parameter tool with no output schema, the definition is minimally viable but leaves real questions open: whether the directory must pre-exist, whether the path is validated against being inside a group workspace, and how the added folder relates to the authorize/remove siblings. A short clause on those points would make it 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% and the single parameter is fully described as "Absolute path of the folder," so the schema already does the work. The description adds only the example of an external disk as a typical location, which is mild context rather than new parameter semantics — the baseline 3 applies.

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?

"Add a folder ... where group models are saved" states a specific verb and resource, and the qualifier "group models" scopes it beyond a generic folder operation, implicitly distinguishing it from bitpull_add_folder-style siblings. It stops short of explicitly naming a contrasting sibling, so it is clear but not maximally differentiated.

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 only usage cue is the example "for example on an external disk," which hints at configuration of a storage location but never says when to choose this tool over the nearby bitpull_authorize_folder, bitpull_remove_model_folder, or bitpull_remove_folder. No prerequisites, no exclusions, no routing guidance.

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