bitbucket_pull_request_comment_list

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and 'List comments' is consistent with those, so there is no contradiction. However, the description adds no behavioral context beyond the annotations — nothing about pagination, ordering, or what the response contains — so it contributes minimal value.

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?

A single clear, front-loaded sentence with zero wasted words. It conveys the essential action efficiently.

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?

For a list tool with no output schema and a non-obvious maxItems parameter, the description is too thin. It fails to mention pagination, default result limits, or return semantics, and gives an agent no help distinguishing comments from tasks via the sibling task_list tool.

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 only 50%; id and maxItems have no schema descriptions, and the tool description adds nothing about any parameter. In particular, maxItems (default 50, max 100) is non-obvious and could benefit from explanation, but the description provides no compensation for the coverage 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 states a specific verb (List) and resource (comments on a pull request), so the core action is clear. However, it does not distinguish itself from nearby siblings like bitbucket_pull_request_task_list (tasks vs. comments) or bitbucket_pull_request_comment_create, so an agent must infer the boundary from names alone.

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?

There is no guidance on when to use this tool versus alternatives. With siblings such as bitbucket_pull_request_comment_create, bitbucket_pull_request_task_list, and bitbucket_pull_request_get, no context or exclusions are given to help an agent choose correctly.

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