loop_start

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

No annotations provided, but description covers key behavioral traits: returns run_id, stores best graph externally for persistence across compaction, enables reversion. Does not mention authorization or rate limits, but adequate for a start tool.

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?

Three paragraphs with clear structure: imperative instruction, parameter explanations, return value and significance. Concise but could be slightly tighter; no wasted sentences.

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?

Fully covers purpose, usage timing, parameter semantics, return value (run_id), and behavioral significance. Output schema exists but description adds value beyond it. Complete for a start 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?

Schema has 2 params with 0% description coverage, but description adds substantive meaning: 'brief is what right means' and 'gate is the objective test'. Compensates for lack of schema-level 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 it opens a loop run, with specific verb+resource ('Open a loop run'). Distinguishes from sibling tools like loop_record, loop_best, etc. by explaining this is step 0.

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?

Explicit timing instruction: 'do this BEFORE the first submit'. Explains when to use 'gate' (if brief has objective test) vs leave empty. Does not explicitly mention when not to use, but context of siblings provides differentiation.

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