run_chain

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose important behaviors: rerouting through master, single-shot checklist returns, session-based freeform chains, and continuation via advance_chain. It stops short of detailing the exact session-start return value or error behavior.

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 four sentences long, and every sentence earns its place: start action, routing guidance, checklist behavior, and session continuation. The core purpose is front-loaded and there is no filler.

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 one-parameter tool with no output schema, the description covers start, routing, and next-step behavior well. The main omissions are a fuller explanation of what PASS means and what the immediate return value is when a session is opened.

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?

The schema already covers the only parameter with examples, and the description reinforces and extends that meaning by explaining how "master" and "default" are used and tying custom chains to list_chains. This adds practical routing context beyond the schema's basic name field.

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 opens with a clear verb and resource: 'Start a thinking chain by name.' It differentiates from siblings by explicitly naming advance_chain for continuation and list_chains for discovering custom chains, so an agent can tell which tool to use.

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?

It gives explicit routing guidance: call a matching chain directly when the task shape matches, otherwise use run_chain("master") to route between PASS, "default", and custom chains. It also clarifies that checklist chains are single-shot while staged/freeform chains open a session and should be continued with advance_chain.

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