bitbucket_get_default_branch

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

There are no annotations, so the description must carry the transparency burden. It discloses the return format (JSON string) and a specific error condition (ValueError when client is not configured). However, it does not address potential domain errors (e.g., repository not found) or mention that this is a read-only operation (though it is implied by 'Get'). The disclosure is minimal but not entirely absent.

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 front-loaded with a one-sentence purpose, followed by structured Args/Returns/Raises sections. Every line adds value—no filler. It is appropriately sized for a simple getter tool and follows a clean, readable format.

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 simple tool with fully documented schema parameters and an existing output schema, the description covers the essential aspects: purpose, inputs, return type, and an error condition. The main gap is lacking usage guidance, but given low complexity, the description is otherwise complete enough for an agent to invoke it 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 description coverage is 100%, with both parameters fully described in the input schema (workspace and repository, including Cloud vs Server/DC distinction). The description's Args section simply repeats the schema text without adding additional meaning. Baseline 3 applies given the high coverage.

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 is specific and clear: "Get the default branch for a repository." It uses a strong verb and identifies the exact resource. This distinguishes it from sibling tools like bitbucket_list_branches (which lists all branches) and bitbucket_get_repository_info (which retrieves general repository details).

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, no prerequisites, and no exclusions. It simply states the operation. There is no mention of scenarios where this would be preferred over other Bitbucket tools, leaving the agent to infer usage solely from the tool name.

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