bitpull_remove_folder

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

The single sentence usefully disambiguates the destructiveHint=false annotation by framing the operation as ceasing to read a folder rather than deleting it from disk. Beyond that it says nothing about what happens to stored folder configuration, whether re-authorization is needed to re-add it, or what the call returns.

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?

A single front-loaded sentence with no filler, and the non-destructive framing appears immediately. It is borderline telegraphic, which leaves little structure for the reader to anchor on but wastes nothing.

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, non-destructive registration tool with a fully documented schema and no output schema, this is close to sufficient; the key ambiguity about disk deletion is resolved. What is missing is any notion of side effects on existing folder configuration and how it relates to the sibling remove tools.

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?

There is one parameter and the schema documents it at 100% coverage ('Absolute path of the folder', with length bounds), so the schema carries the semantics. The description adds no format hints, path expectations, or examples beyond that baseline.

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 gives a specific verb and resource ('Stop BitPull reading a folder'), which is clearer than the tool name's 'remove', since it signals the folder is unwatched rather than deleted. It does not, however, distinguish itself from siblings like bitpull_remove_model_folder or bitpull_remove_repo, so an agent must infer which resource type applies.

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 when-to-use guidance, no exclusions, and no stated alternatives such as swapping a folder for another or pausing rather than removing. The agent learns what the tool does but not when to prefer it over bitpull_remove_model_folder or bitpull_add_model_folder.

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