reject_branch

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

Description adds scope ('all open drafts') beyond destructiveHint annotation. However, does not explain whether drafts are deleted, archived, or if branch is affected.

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?

Single sentence, no wasted words. Could benefit from structured parameter details, but remains concise.

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?

Output schema exists but description says nothing about return values. For a destructive tool, lacks explanation of consequences. Given sibling complexity, description is overly minimal.

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 0% and description does not mention parameters. Two parameters (branch_id, reason) are left undocumented in description, failing to compensate for lack of schema descriptions.

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?

Clearly states action 'Reject' and resource 'all open drafts in a branch/session'. Distinguishes from siblings like reject_draft (single draft) and merge_branch.

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 explicit when to use or alternatives. Siblings include reject_draft for single drafts, but description does not differentiate. destructiveHint annotation implies caution, but no usage guidance.

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