bisect_start

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

No annotations provided, so description carries full disclosure burden. Describes behavioral traits: enables half, disables rest, uses HTTP API first with fallback to local, and may require restart. Adequately transparent.

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?

Concise: three sentences, no redundancy. Front-loaded with core purpose, followed by method and technical details. 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?

Given no input schema parameters and no output schema, the description covers purpose, process, technical fallback, and restart requirement. Sufficient for an agent to understand and invoke correctly.

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?

Input schema has zero parameters; description is not required to add parameter info. Baseline is 4, and description meets this by staying silent on parameters.

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 it begins a binary-search session to find problematic custom nodes. Uses specific verbs ('Begin', 'guide') and distinguishes from siblings by naming bisect_good/bisect_bad as subsequent steps.

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 clear context: used for finding which custom node causes a problem, outlines the process. Does not explicitly state when to avoid or list alternative siblings, but mentions fallback behavior and restart need.

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