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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that: the operation is scoped to pull requests 'the user has access to' and requires a connected GitHub integration, which tells the agent about auth prerequisites and permission scoping.

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?

Two tightly written sentences: the capability and its scope come first, the prerequisite second. No filler, no restatement of the title.

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?

A 7-parameter tool with a 9-value enum mode selector and no output schema needs more than this. The description never explains the relationship between the 'method' values and the returned content, nor mentions pagination handling, so an agent must fall back entirely on the schema to choose a mode.

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 every parameter (including the method enum with its retrieval modes and the pagination cursors) is already documented in the schema. The description's list of retrievable content loosely echoes a few method values but adds no syntax, defaults, or constraints beyond what the schema provides — baseline 3.

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?

States a specific verb (read) and resource (GitHub pull request) and enumerates the kinds of content available (description, changed files, review comments, status). It is clearly distinguishable from its actual siblings (get_file_contents, get_me, search), though it does not name them explicitly.

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?

It gives a prerequisite ('Requires a GitHub integration connected by the user'), which is real usage guidance, but offers no when-to-use/when-not guidance and no hint about which of the nine 'method' modes to pick. With 'method' being the primary routing parameter, the absence of mode selection advice is a clear gap.

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