get_bitbucket_repo

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

With no annotations provided, the description must convey behavioral traits. It only says 'Fetch', implying read-only, but does not clarify behavior on missing repo, error handling, rate limits, or any side effects. Insufficient for an agent to understand the tool's full behavior.

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. However, it lacks structure; no separation of purpose, parameters, or behavior. Every word earns its place, but the overall value is low due to brevity.

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 tool's simplicity (2 params, no annotations) and existence of an output schema, the description should still specify parameter roles and scope. It fails to mention that workspace is optional, what metadata is returned, or any limitations. Incomplete for reliable agent use.

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 input schema has 2 parameters (repo_slug, workspace) with 0% description coverage. The tool description does not explain these parameters, their purpose, format, or defaults. The agent cannot infer what values to provide beyond parameter names.

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 'Fetch Bitbucket Cloud repository metadata' clearly states the action (fetch) and resource (repository metadata). It implicitly distinguishes from siblings like list_bitbucket_repos (list) and search_bitbucket_repos (search), though it could be more explicit about fetching a single repo's details.

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 on when to use this tool versus alternatives such as list_bitbucket_repos or search_bitbucket_repos. The description does not specify that it retrieves a specific repository by slug, nor does it mention prerequisites or best use cases.

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