bb_get_pull_request_activity

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

With no annotations, the description carries the full burden for behavioral disclosure. It states what information is returned (reviews, approvals, comments) but does not mention pagination behavior, response format, ordering, or clearly state that it is a read-only operation. This is a minimal disclosure, not a transparent behavioral specification.

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 that states the action and the key categories of activity. Every word earns its place with no fluff or redundancy.

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?

The tool has 7 parameters and no output schema, but the schema itself documents all parameters and the output_format parameter covers response style. The description gives enough to select the tool, yet it omits any guidance on pagination, filtering, or what the response structure looks like, leaving some gaps for an agent.

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%, so the baseline is 3. The description does not add any meaning beyond the schema; the parenthetical about activity types relates to the endpoint's purpose, not to specific parameters like page, pagelen, or filter.

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 uses a specific verb ('Get') and resource ('activity for a specific pull request'), and immediately clarifies what counts as activity ('reviews, approvals, comments'). This clearly distinguishes it from sibling tools like bb_get_pull_request_comments or bb_get_pull_request.

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 implies usage: use this when you need activity for a specific pull request, not a list of pull requests. However, it does not explicitly state when to prefer this over sibling tools such as bb_get_pull_request_comments, nor does it mention any exclusions or alternatives.

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