bb_get_pull_request_comments

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It does not mention pagination, ordering, response shape, or any side effects. While it is clearly a read operation, the lack of behavioral detail (e.g., paginated by default, possibly large result set) leaves the agent to infer from the schema.

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, front-loaded sentence with no wasted words. It is concise and to the point. However, it is minimal to the point of under-specification, but that is more a completeness issue than a conciseness issue. It earns its place without being verbose.

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 complexity (7 params, no annotations, no output schema), the description is too minimal. It does not mention pagination, filtering, or the relationship to sibling tools like bb_get_pull_request_comment. The schema covers parameter semantics but not overall behavior, leaving the agent without sufficient context to invoke the tool correctly in varied scenarios.

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% for all 7 parameters, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides. It does not explain how parameters like 'filter' or 'page' affect the call, but the schema covers them adequately.

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 the action 'Get' and the resource 'comments for a specific pull request'. It distinguishes from sibling tools such as bb_get_pull_request (which fetches the pull request itself) and bb_get_pull_request_comment (which may fetch a single comment). The verb+resource combination is specific and unambiguous.

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 is provided on when to use this tool versus alternatives. The sibling tool bb_get_pull_request_comment is ambiguous, and the description does not clarify that this tool returns all comments or how it differs from a single-comment fetch. No context, exclusions, or alternatives are mentioned.

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