create_repository

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions that the repository will be created and returns clone URLs, it doesn't address important behavioral aspects like required authentication, potential rate limits, whether the operation is idempotent, or what happens if a repository with the same slug already exists. This leaves significant gaps for an agent to understand the tool's behavior.

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 well-structured with clear sections for Args and Returns, making it easy to parse. It's appropriately sized with no redundant information, though the formatting with quotes around the entire description is slightly awkward. Every sentence serves a purpose.

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 creation tool with 4 parameters and no annotations or output schema, the description provides basic parameter semantics and return information but lacks important contextual details. It doesn't explain error conditions, authentication requirements, or how the tool fits into broader workflows. The absence of an output schema means the description should ideally provide more detail about the return structure.

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?

The description provides meaningful semantic information for all parameters beyond what the schema offers (0% coverage). It explains that 'repo_slug' must be lowercase with no spaces, 'project_key' is optional, 'is_private' defaults to True, and 'description' is for repository description. This adds substantial value over the bare schema field names.

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 clearly states the specific action ('Create a new Bitbucket repository') with the resource type, distinguishing it from sibling tools like 'update_repository' or 'delete_repository'. It uses precise language that leaves no ambiguity about the tool's function.

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 provides no guidance on when to use this tool versus alternatives like 'update_repository' or 'get_repository', nor does it mention prerequisites such as required permissions or project existence. It lacks context about when this operation is appropriate versus other repository-related tools.

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