bb_create_repository

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false, so this is understood to be a mutating, non-idempotent operation. The description adds no extra behavioral context beyond that, such as whether creating a repository with an existing name fails, whether it interacts with issues/private defaults, or what access is required. With annotations present, a 3 is reasonable but the description could add more.

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 clear sentence, appropriately brief. However, it is the minimum viable statement: it doesn't add any contextual information beyond the tool name and resource. It is concise but lacks enriching detail that would make it more helpful.

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 schema covers all parameters and there is an output schema, the description is functionally sufficient. However, it doesn't communicate important context such as how the workspace and project_key interplay, the fact that '~' targets personal workspace (already in the schema), or any constraints like naming rules. It is adequate but not 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 parameters are already well documented in the schema. The description itself adds no parameter-level detail. Baseline 3 applies since schema carries the load; no additional value is provided by the description.

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 in Bitbucket.' This clearly differs from sibling tools like bb_create_branch or bb_create_issue. However, it lacks detail about workspace/project context that would help distinguish from other create-family tools.

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 gives no explicit when-to-use guidance or alternatives. However, the tool name and description naturally imply its use case: creating a new repository. The workspace and project_key parameter descriptions hint at the required context, but no explicit guidance is given about when to use this vs. other tools.

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