until

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

No annotations exist, so the description carries the full burden. It notes 'Blocks until stopped' and skips loops without temporary breakpoints, but does not disclose timeout behavior (though timeout param exists) or what happens if location is never reached.

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 sentences, each earning its place: first defines purpose, second adds behavioral nuance, third details the key parameter. No waste.

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?

The description is complete regarding what the tool does but lacks parameter descriptions for session_id and timeout, and does not mention return value or output schema. For a tool with 3 parameters and no schema descriptions, more detail would be beneficial.

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 description coverage is 0%, so the description must explain parameters. It thoroughly describes the 'location' parameter with examples. However, 'session_id' and 'timeout' are not explained at all; timeout's default is not contextualized.

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 clearly states the tool runs forward until a specific location is reached, with distinctive behavior: skipping loops and blocks without setting temporary breakpoints. This distinguishes it from siblings like step, next, or finish.

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?

The description implies when to use (run to a location without breakpoint) but does not explicitly state when not to use or compare with alternatives. The hint about skipping loops implicitly suggests avoiding it when loop stepping is desired.

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