bb_list_repositories

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

With no annotations, the description carries the behavioral transparency burden. It does disclose important traits: it returns a list, supports server-level or project-scoped listing, includes specific item fields, and is paginated. However, it does not describe the response envelope, default pagination behavior, or any error/auth requirements, which is a noticeable gap.

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?

Two tight sentences deliver the core behavior, scope options, item contents, and pagination. There is no filler or repetition, and the most important scoping information is front-loaded.

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 list tool with 4 parameters and no output schema, the description gives a reasonable overview but omits details an agent needs for robust invocation: pagination parameter semantics, default limits, response structure, and how the filter interacts with server-level vs project-scoped listing. It is adequate but not fully 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 50%, and the description adds only modest value: it restates the projectKey scoping concept ('no filter' vs 'scoped to one project') and mentions pagination generally. The limit and start parameters remain undocumented in both schema and description, and the filter parameter's meaning is only fully explained in the schema. The description partially compensates but does not close the gaps.

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 names the verb (List), the resource (GIT repositories), and the two scopes (all server-level or one project). It also lists the returned per-item fields, making the tool's purpose concrete. It does not explicitly contrast with siblings like bb_search_repositories or bb_get_repository, so it stops short of a 5.

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 clear context: use no filter for server-wide listing or provide a project scope. It does not explicitly state when not to use this tool or when to prefer bb_search_repositories or bb_get_repository, but the scope guidance is strong enough for an agent to decide basic usage.

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