approve_pull_request

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

No annotations are present, so the description carries full responsibility. It merely states 'Approve a pull request' without disclosing mutating effects, permission requirements, reversibility, notifications, or potential side effects. For a write operation, this is a critical omission.

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 concise and well-structured, with a one-line purpose followed by an args list. No terse or redundant language. It loses a point because it is so sparse that it borders on under-specification, but that is more relevant to completeness than conciseness.

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?

With no annotations and no visible output schema, the description fails to cover critical context: return values, error conditions, permission requirements, or how approval affects the PR workflow. For a mutating tool, this is significantly incomplete.

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%. The description lists parameter names with minimal descriptors ('PR ID number', 'Workspace slug', 'Repository slug') but does not explain requiredness, defaults, or how workspace/repo are resolved when omitted. This adds very little beyond the schema's type information.

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 'Approve a pull request' with a specific verb and resource. This clearly distinguishes the tool from sibling operations like merge_pull_request, decline_pull_request, or request_changes_on_pr.

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 unapprove_pull_request, request_changes_on_pr, or other review actions. It lacks context about prerequisites, workflow placement, or exclusions.

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