close_branch

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

Discloses key behaviors: branch and thoughts preserved, cannot be reopened. With no annotations, description adequately covers behavioral traits. Minor gap: no mention of permissions or side effects.

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?

Four sentences well-structured: action, option, preservation, usage guidance. Front-loaded with core purpose.

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?

Complete for simple tool with two params. Describes what happens and usage context. No output schema needed.

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 has 100% coverage and description mentions optional conclusion, but adds no new detail beyond schema descriptions. Baseline 3 appropriate.

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 'Close a branch' and resource. Explicitly distinguishes from sibling merge_branch by advising to use it instead for bringing findings back to main.

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?

Provides explicit when-to-use ('line of reasoning exhausted or answer clear') and when-not (cannot be reopened, suggests merge_branch as alternative).

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