bisect_bad

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

No annotations provided; description discloses key behaviors: marks bad, narrows, enables next, resolves culprit. Lacks details on side effects or prerequisites, but sufficient for a bisection step.

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?

Two concise, front-loaded sentences with no fluff. Every sentence adds value.

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?

Explains the process and outcome clearly. No output schema, but description covers the main effect. Missing error handling details, but adequate for a specialized bisection tool.

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?

No parameters, so schema coverage is 100% trivially. Baseline 4 applies; description adds no parameter info, but none needed.

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 the tool marks the current set as BAD, narrows bisection, and reports culprit. Distinguishes from siblings like bisect_good and bisect_reset by using opposite semantics.

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?

Describes when to use (problem present with set) and what happens next. Does not explicitly mention when not to use or alternatives, but context of bisection is clear.

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