Github Get Pr Content

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Fetches' wording is consistent and the safety profile is covered. The description adds minimal behavioral context beyond that, such as the scope being a single specified pull request, but it does not disclose additional traits like authentication requirements or rate limits.

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 and front-loaded with the main purpose. The workflow line is a bit cryptic but not padded; overall it is efficient and easy to scan.

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?

Output schema and annotations carry some contextual weight, so the description does not need to explain return values or read-only behavior. However, it lacks sufficient parameter guidance and sibling differentiation, making it minimally viable but not fully complete for correct tool selection and invocation.

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 0%, and the description does not explain repo_owner, repo_name, or pr_number semantics beyond the generic phrase 'a specific pull request'. The parameter names are self-explanatory, but the description fails to compensate for the missing schema-level documentation.

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 a clear verb ('Fetches') and resource ('content/details of a specific pull request'), making the basic purpose obvious. However, it does not differentiate from sibling tools like github_get_pr_diff or github_get_pr_linked_issues, so the agent must infer the exact distinction from the tool name.

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 only usage-related content is the terse instruction 'Workflow and conventions: github_get_skill("pr-analysis")', which tells the agent to load a skill but not when to prefer this tool over alternatives. There are no conditions, exclusions, or explicit comparisons with sibling PR-related tools.

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