bb_create_repository

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

With no annotations provided, the description carries the burden of behavioral disclosure. It goes beyond the basic 'create' by stating defaults: empty repo with initial 'master' branch, private visibility. It also notes the forkFrom behavior. It does not mention permissions or irreversibility, but the core behavioral traits are disclosed.

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 two sentences with no redundant language. It front-loads the main purpose and then adds key defaults and a conditional. Every word contributes information.

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 7-parameter creation tool with no output schema and no annotations, the description conveys the essential behavior and defaults while the schema handles parameter details. It could add a note about the interaction between forkFrom and emptyRepo, and what happens on success, but overall an agent has enough to call correctly.

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 high at 86%, so the description need not explain every parameter. It adds minor value by clarifying the default branch name ('master') and tying 'private' to isPublic. However, most parameter meaning is already captured in the input schema.

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 states a specific verb and resource: 'Create a new repository under an existing project.' It clearly distinguishes from siblings like list, get, search, file, and branch operations. The defaults and fork option further define the tool's scope without ambiguity.

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?

It gives clear context by stating this is for creating a repository under an existing project, implying the prerequisite that a project already exists. It also explains the fork condition ('Set forkFrom to fork from another repo'). It does not explicitly name alternative tools, but the usage context is clear enough.

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