bb_list_repositories

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

Without annotations, the description must disclose behavioral traits but only states 'List repositories'. It does not confirm this is a read-only operation, mention any authentication or permission requirements, or describe pagination behavior (though pagination parameters exist). The lack of detail forces the agent to infer behavior from the schema alone.

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 sentence with no fluff, making it concise. However, it is arguably too short and misses important context; a slightly longer description could improve completeness without sacrificing conciseness.

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 tool has four parameters (including pagination and filtering) and no output schema, the description should explain the listing behavior, pagination details, and return value structure. It fails to do so, leaving the agent with insufficient context to use the tool effectively.

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 all parameters are documented in the input schema. The description adds no extra meaning beyond the schema (e.g., it does not explain how the 'query' parameter works or the default for 'workspace'). Baseline 3 is appropriate since the schema already does the heavy lifting.

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 action ('List') and resource ('repositories in a Bitbucket workspace'), which distinguishes it from sibling tools that list other entities like branches or pull requests. However, it does not specify the scope (e.g., all repositories in the workspace) or mention that the workspace parameter is optional and defaults, slightly reducing clarity.

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?

No guidance is provided on when to use this tool versus alternative listing tools (e.g., bb_list_branches, bb_list_commits). There is no mention of prerequisites, potential use cases, or when not to use it.

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