getPullRequestActivity

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds little behavioral detail beyond what the annotations provide, and does not mention pagination, ordering, or the types of events included in the timeline.

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 filler or redundant explanation. It states the verb and resource immediately and earns its place without unnecessary detail.

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 simple read-only tool with fully documented parameters and strong annotations, the description is minimally adequate. However, with no output schema, the description does not clarify what 'activity/timeline' includes, which could confuse an agent deciding between this and more specific sibling tools like getPullRequestComments or getPullRequestCommits.

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%, with all three parameters (owner, repo, pull_number) documented in the input schema. The description adds no additional parameter-level meaning, matching the baseline for full schema coverage.

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 clear verb ('Get') and resource ('activity/timeline of a pull request'), making the tool's core function evident. It is distinguishable from sibling tools like getPullRequest (PR details) or getPullRequestComments (specific comments), though the meaning of 'activity/timeline' is somewhat broad.

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?

There is no explicit guidance about when to use this tool versus siblings such as getPullRequestComments, getPullRequestCommits, or getPullRequestDiff. The usage is only implied by the phrase 'activity/timeline', so an agent must infer that this provides a broader view than those more specific tools.

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