bitbucket_pull_request_activities

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

With no annotations, the description must disclose behavioral traits. It mentions returning a JSON string and raising ValueError, but fails to describe pagination, authorization requirements, or what types of activities are included. The mention of 'comments' in the parameter description is misleading.

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 short but contains an inaccuracy: the Returns section says 'list of pull requests' instead of 'list of activities.' This undermines trust. While concise, every sentence should be accurate.

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?

Despite having an output schema, the description misstates the return value as 'pull requests' instead of activities, creating confusion. It also omits details about the scope of 'activities' (e.g., comments, status changes, approvals).

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?

The input schema has 100% description coverage, so the baseline is 3. The description repeats parameter names and adds context for workspace, but the schema already provides that context. No new semantic information is added.

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 'Get all activities on a pull request,' which identifies the action and resource. However, the parameter description for pull_request_id says 'to get comments for,' conflating activities with comments, creating ambiguity about the exact purpose.

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 like bitbucket_get_pull_request or bitbucket_add_pull_request_comment. The description does not specify scenarios or exclusions.

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