bitbucket_repositories

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

No annotations are provided, so the description bears full responsibility. It does not disclose behavioral traits such as whether actions are read-only or destructive (e.g., delete is destructive but not flagged). No information on authentication requirements, rate limits, side effects, or response behavior is given.

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 concise with a bullet list of actions. It is front-loaded with 'Manage Bitbucket repositories' and then enumerates actions efficiently. No redundant information is present, but some structure could be improved by grouping actions or adding brief parameter context.

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 (17 parameters, 7 actions, no output schema), the description is incomplete. It does not explain return values, pagination handling, or how the 'action' parameter selects behavior. Missing context on parameter dependencies and result formats leaves agents underinformed.

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 baseline is 3. However, the tool description adds no meaning beyond the schema; it only lists actions without mapping which parameters apply to each action. For example, 'name' is for create but not indicated. This omission reduces the value, making it harder for agents to understand parameter usage context.

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 it manages Bitbucket repositories and lists specific actions like list, get, create, delete. This provides a clear verb+resource mapping for each action. However, it does not explicitly differentiate from sibling tools, though the resource type (repositories) is distinct from branches, commits, etc.

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 sibling tools (e.g., bitbucket_branches, bitbucket_issues). There are no conditions, prerequisites, or alternatives mentioned. The list of actions implies usage but lacks explicit when-to-use context.

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