Code Review MCP

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this is read-only, requires authentication, has rate limits, returns paginated results, or what 'fetch' entails (e.g., diff format, file content). This leaves significant gaps for a tool that likely interacts with external APIs.

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 extremely concise with a single phrase 'Fetch files/diff for a PR', which is front-loaded and wastes no words. Every part earns its place by stating the core action and target, making it efficient for quick understanding.

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 no annotations, 0% schema coverage, no output schema, and 3 parameters, the description is incomplete. It lacks details on behavior, parameter meanings, return values, and usage context. For a tool fetching PR files, this minimal description doesn't provide enough information for an agent to use it effectively without guesswork.

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%, so the description must compensate but adds no parameter semantics. It doesn't explain what 'owner', 'repo', or 'pull_number' mean, their formats, or constraints. With 3 undocumented parameters, the description fails to provide essential context beyond the schema's basic types.

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 'Fetch files/diff for a PR' states a clear verb ('fetch') and resource ('files/diff for a PR'), but it's vague about scope and doesn't distinguish from sibling tools like 'github.resolve_pr' or 'code-review'. It specifies what it does but lacks detail on what 'fetch' entails (e.g., full content vs. metadata).

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., after PR creation), or exclusions, and sibling tools like 'github.resolve_pr' or 'code-review' might overlap without clarification. The description implies usage for PR files but offers no explicit when/when-not instructions.

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