approve_pr

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. It states the action ('Approve') but doesn't describe what approval entails (e.g., whether it's reversible, if it requires specific permissions, what happens to the PR status, or any side effects). This is a significant gap for a mutation tool.

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 efficiently structured with clear sections (purpose, Args, Returns) in just three sentences. Every element serves a purpose with no wasted words, though the 'Returns' section could be slightly more informative.

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 mutation tool with no annotations and no output schema, the description adequately covers the basic purpose and parameters. However, it lacks important context about behavioral aspects (permissions, side effects, return format) and usage guidelines relative to sibling tools, leaving gaps for an AI agent.

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 description explicitly documents both parameters ('repo_slug' and 'pr_id') in the Args section, providing clear semantic meaning. Since schema description coverage is 0%, this documentation fully compensates for the schema's lack of descriptions, making parameters well-understood.

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 the action ('Approve') and resource ('a pull request'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'unapprove_pr' or 'merge_pull_request' which are related approval/merge operations on pull requests.

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 about when to use this tool versus alternatives like 'unapprove_pr', 'decline_pr', or 'merge_pull_request'. The description lacks any context about prerequisites, permissions needed, or typical workflow scenarios.

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