bitpull_start_group

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

Annotations supply only destructiveHint=false, so the description must carry the behavioral burden. It doesn't say whether starting requires prior authorization of folders or a connected account, whether the model is downloaded first, what happens if it's already running, or what the response contains. A mutating, infrastructure-touching action is described in one vague sentence.

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?

It is short, but the brevity comes at the cost of clarity: "the person's computers" and "for the person's own use" are vague phrasing rather than compressed information. The second sentence is awkwardly front-loaded with "Optional custom:" and reads like a schema fragment rather than guidance.

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?

This is a nested-object tool with no output schema and minimal annotations, so the description has to do real work. It omits prerequisites, the meaning of the required model parameter, the format of repo/file, and any outcome information — not enough for an agent to invoke it confidently.

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 0%, so the description must explain both params. It partially explains "custom" as a Hugging Face GGUF but never states the expected format of repo (owner/name?) or file, and it says nothing about the required "model" param — whether it is a name, ID, or path, or whether it must already exist in the group's model list.

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 verb and resource ("Start a model on the person's computers in their network"), but the phrasing is loose and never clarifies what "start" means operationally, nor how it differs from the sibling bitpull_start_app, which sounds near-identical. An agent could guess, but it cannot distinguish the two tools from this text.

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 explicit when-to-use or when-not-to-use guidance and no named alternative such as bitpull_start_app, bitpull_group_preview, or bitpull_stop_group. The only conditional hint is that "custom" is optional, which is about a parameter, not about choosing this tool.

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