list_bitbucket_repos

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'list', implying a read operation, but lacks details on pagination, ordering, rate limits, or whether it returns all repos accessible in the workspace. The presence of a 'max_results' parameter hints at pagination, but the description does not confirm or explain it.

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, concise sentence with no wasted words. However, it lacks necessary detail, making it less informative. It is neither overly verbose nor well-structured for helpfulness.

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 0 required parameters but 3 optional ones with no descriptions, and no annotations, the description is insufficient. It does not cover the input parameters, output behavior, or any edge cases. The existence of an output schema is not leveraged.

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 0%, so the description must explain each parameter. It does not mention 'workspace', 'role', or 'max_results' at all, leaving their meaning and usage entirely undocumented. This is a critical gap.

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 verb 'list' and the resource 'Bitbucket Cloud repositories in a workspace', which is specific. However, it does not explicitly clarify that the 'workspace' parameter is required to scope the listing, leaving slight ambiguity about the scope. It is clear enough to differentiate from sibling tools like search_bitbucket_repos.

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 like search_bitbucket_repos or get_bitbucket_repo. There is no mention of use cases, prerequisites, or limitations.

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