list_repositories

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior, or what happens when no repositories exist. For a list tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose with no wasted words. Every element ('List all repositories,' 'in the configured Bitbucket workspace') directly contributes to understanding the tool's scope and action.

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 complexity of a list operation with parameters, no annotations, and no output schema, the description is incomplete. It lacks details on return format, error handling, pagination, or how parameters affect results. For a tool with 2 parameters and no structured output documentation, more context is needed to guide the agent 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 the schema fully documents both parameters. The description adds no parameter-specific information beyond what's in the schema, such as explaining why 'include_commit_info' might be useful or how 'limit' interacts with pagination. Baseline 3 is appropriate when the schema does all the work.

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 all repositories') and the resource ('in the configured Bitbucket workspace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_repository_details' or 'list_workspaces', which would require mentioning it returns a collection rather than single items or workspace metadata.

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 implies usage context by specifying 'all repositories in the configured Bitbucket workspace,' suggesting this is for bulk retrieval. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_repository_details' for single repos or 'list_workspaces' for workspace-level info, leaving some ambiguity for the agent.

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