list_repositories

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

There are no annotations, so the description must carry the behavioral burden. 'List' suggests a read-only operation, but the description does not disclose potential pagination behavior, whether it returns all results in a single call, or how workspace resolution works when not provided. It is not misleading, but it is thin on behavioral nuance.

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 two short, efficient sentences. The first conveys the core action and scope, the second lists the return fields, with no wasted words or redundancy.

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 one-parameter tool, the description and schema together provide enough context to call it: the workspace parameter is documented, and the return values (names, slugs, descriptions, links) are explicitly listed. A small gap is the lack of mention of pagination or any limits, but 'all repositories' implies the tool handles that.

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 schema description fully covers the single optional parameter, including its meaning and fallback environment variable, so the description does not need to add details. Baseline 3 is appropriate because the schema already provides 100% 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 clearly states a specific action ('List') on a specific resource ('repositories') scoped to 'a Bitbucket workspace,' and adds what it returns. It semantically differentiates from siblings such as get_repository by emphasizing 'all repositories.'

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 given for when to use this tool over siblings such as get_repository or list_workspaces, nor are any exclusions or prerequisites mentioned. The description only states what it does, leaving the agent to infer context.

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