bitbucket_repository_list

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

Annotations already declare readOnlyHint and idempotentHint, so the main side-effect profile is covered and there is no contradiction. The description itself adds little behavioral context beyond the workspace scope; it does not mention pagination, result limits, or how the query parameter affects the returned list.

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, clear sentence with no filler or redundant content. It fronts the core operation and object type and earns every word that is present.

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?

The schema and read-only annotations make the tool callable correctly, but the description itself is thin in this Respect: it does not mention response shape, query flexibility, or the optional nature of the parameters beyond what the schema already states. For such a simple list tool this is acceptable but not guiding.

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 does not add parameter-level meaning; it does not discuss the query filter, workspace default, or maxItems. However, schema descriptions already cover query and workspace and constrain maxItems with default/min/max values, so the 67% schema coverage keeps this at a baseline rather than a failure.

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 uses a specific verb ('List') and a distinct resource ('repositories') scoped to 'a workspace.' This makes the tool's purpose clear and separates it from resource-specific get/retrieve tools, though it does not explicitly name or contrast sibling tools.

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 choose this tool over alternatives such as bitbucket_repository_get, bitbucket_code_search, or other list tools. It relies on the agent to infer the use case from the name and the operation, providing no exclusions or alternative conditions.

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