bb_list_pull_request_comments

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

No annotations are provided, so the description carries the disclosure burden. It reveals the output shape (id, text, author, state, anchored line/lineType, web link) and states that results are paginated. It does not cover ordering, filtering details, or auth requirements, but it is transparent about the core read 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 three sentences with no filler: verb and resource are front-loaded, then output fields and pagination are listed compactly. Every sentence adds value.

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 read-only list tool with no output schema or annotations, it provides the return-field details and pagination behavior. The important path-filtering semantics are present in the schema description, which mitigates the gap, though the tool description itself could have repeated that requirement.

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 33%, and the tool description does not compensate. It adds only the generic hint 'Paginated' for limit/start, while omitting crucial guidance about the path parameter's required role and the meanings of other parameters.

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 opens with a specific verb 'List' and resource 'comments on a PR', and clarifies scope with 'including global and inline code comments'. This clearly distinguishes it from sibling comment mutation tools like create/update/delete/resolve comment.

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 gives a clear context for use: retrieving PR comments, including global and inline ones. It does not explicitly name alternatives or exclusions, but the stated purpose makes the appropriate use case unambiguous.

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