get_bitbucket_pull_request

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

No annotations are provided, so the description must fully disclose behavior. It only says 'fetch details' but does not confirm read-only nature, authentication needs, rate limits, or any side effects. The user cannot infer behavioral traits beyond the implied idempotent read.

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 extremely concise at 6 words, which is efficient but omits critical information. It is not verbose, but the brevity comes at the cost of clarity and completeness. The structure is front-loaded but insufficient.

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 that an output schema exists (context signal), the description does not need to explain return values. However, with 3 parameters (1 optional) and no annotations, the description is too sparse. It does not mention that workspace is optional or the ordering of required parameters. The overall context provided is inadequate for safe tool 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?

Schema description coverage is 0%, and the description adds no meaning to the three parameters (repo_slug, workspace, pull_request_id). It does not explain what each parameter is, acceptable formats, or defaults (e.g., workspace defaulting to empty string is undocumented). The description fails to compensate for the low schema coverage.

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 pull request details' clearly states the verb (Fetch) and resource (pull request details), indicating a read operation for a single pull request. It effectively distinguishes from sibling tools like list_bitbucket_pull_requests, which lists PRs, though it does not explicitly differentiate in the text.

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. It does not mention prerequisites, when to use get vs list, or typical use cases. Sibling tools such as list_bitbucket_pull_requests exist, but no comparison is given.

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