get_pull_request_activities

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does list the types of activity returned, which is helpful, but it omits critical behavioral details such as sorting order, default result size, error behavior, and authentication requirements. The claim about filtering is unsupported by the schema, adding confusion rather than transparency.

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 concise and front-loaded, expressing the core purpose in the first sentence and adding a single worthwhile detail about filtering in the second. No wasted words or repetitive content. It is appropriately sized for the tool's complexity.

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 absence of an output schema and annotations, the description should provide more context about return values, ordering, pagination behavior, or use cases. It lists activity types but lacks sufficient detail for an agent to confidently predict the response shape or handle errors. This is a relatively complex tool with many siblings, so the description is incomplete.

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?

All five parameters have descriptions in the schema, so schema coverage is 100%. The description adds no parameter-specific meaning beyond what the schema already provides, and the 'filter by activity types' mention does not map to any parameter. This matches the baseline of 3 for high schema coverage, as the description does not enhance or clarify parameter usage.

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 tool retrieves activity on a pull request, enumerating content types (comments, approvals, merges, reviews, updates). This provides a specific verb and resource, and distinguishes it from sibling tools focused on single activity types like commits or tasks. However, the 'Can filter by activity types' claim is vague and not reflected in the schema, slightly dampening clarity.

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 no explicit guidance on when to use this tool versus alternatives. While listing activity types implies a broader scope than siblings like get_pull_request_tasks or get_pull_request_commits, it does not explicitly state when to prefer this tool or when to use another. No exclusions or alternative tools are mentioned.

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