decline_pull_request

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it offers no additional information. It does not state whether declining is reversible, what side effects occur (e.g., closing the PR), or any permission requirements. For a mutation action, this is a significant gap.

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 (one sentence, five words), which is structurally clean and front-loaded. However, it is under-specified; while not bloated, it sacrifices helpful content for brevity. It meets the minimum threshold but does not add value beyond the tool name.

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 destructive action like declining a pull request, the description is incomplete. There is no output schema and no annotations, so the description should explain return values, side effects, or error conditions, but it does none of this. The description is minimally viable but leaves critical gaps for an agent to use it correctly.

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 coverage is 100%, so the input schema already documents all three parameters (reason, repository, pull_request_id) with descriptions. The tool description adds no extra parameter information, matching the baseline for high schema coverage. The description does not clarify parameter relationships or constraints beyond the schema.

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 'Decline a pull request' clearly states the action (decline) and the resource (pull request). It is unambiguous, though it does not explicitly differentiate from sibling tools like approve_pull_request or merge_pull_request. The verb is specific enough that the purpose is clear.

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. There is no mention of prerequisites, conditions for declining, or situations where another pull request action would be more appropriate. The description simply restates the action without context.

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