remove_change_request_pull_request

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

The description discloses the key behavioral outcome (status reset to UNAPPROVED) but lacks details on prerequisites, side effects, or error conditions. No annotations are provided, so the description carries full burden; it is adequate but not comprehensive.

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 minimal and efficient: two sentences plus a parameter list. It is front-loaded with the primary action and immediate effect, with no redundant information.

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 straightforward tool, the description covers the core behavior and parameters. However, it does not differentiate from similar tools like 'unapprove_pull_request' or mention edge cases, leaving some gaps given the number of siblings.

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%, but the parameter names (project_key, repo_slug, pr_id) are self-explanatory. The description restates these names without adding extra meaning or constraints, so minimal value beyond 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 clearly states the action ('Remove your change request from a pull request') and details the effect ('Resets the user's participant status to UNAPPROVED'). This distinguishes it from sibling tools like 'request_changes_pull_request' and 'unapprove_pull_request'.

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 description implies when to use (when you want to remove your change request) but does not explicitly compare with alternatives or state when not to use. Given sibling tools like 'unapprove_pull_request', more guidance would be helpful.

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