Fetch Pull Requests

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

With no annotations, the description carries the full burden of disclosure. It only says 'Retrieves a list' but does not disclose that the default behavior fetches not-merged PRs (isMerged=false), the default limit of 10, authentication requirements, or return format. This is a significant gap given the tool name implies merged PRs.

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 appropriately sized with two sentences. The first sentence clearly states the purpose, and the second provides usage context. Every sentence earns its place and there is no wasted verbosity.

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?

Even though the schema handles parameter details, the description lacks critical behavioral context such as default merged/not-merged behavior, limit handling, output format, and authentication needs. For a tool with no output schema and no annotations, this is insufficient for an agent to invoke correctly without surprises.

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 schema covers all 4 parameters with detailed descriptions, so the description adds no additional parameter semantics beyond what the schema already provides. Baseline of 3 is appropriate since the description does not compensate for any missing parameter context.

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 it 'Retrieves a list of Pull Requests from the specified GitHub repository', which is specific with a verb, resource, and scope. It distinguishes from sibling tools like get_git_log or get_git_diff, but it does not explicitly mention 'merged' PRs as the tool name suggests, leaving a slight ambiguity.

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 provides clear usage context: 'Crucial for generating automated release notes, writing changelogs, or summarizing the latest features and bug fixes'. However, it does not state when not to use it or mention alternatives, as no sibling comparisons are made.

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