run_goal

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

Discloses key behaviors: immediate return, durability, server-side execution, survival of disconnection. No annotations exist, so description carries full burden; lacks error handling or auth details but is sufficient.

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 sentences, each earning its place: first defines purpose, second explains behavior and next steps. No redundancy.

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 low complexity (one parameter, output schema exists), the description covers the essential workflow. Could mention the output schema explicitly, but it's not missing critical information.

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?

With 0% schema description coverage, the description fails to elaborate on the goal parameter beyond its name. No format, examples, or constraints provided, leaving the agent to infer valid inputs.

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 starts a durable Highway agent that pursues a goal to completion. It distinguishes from sibling tools like schedule_goal and get_status by focusing on immediate execution.

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 guidance: returns a workflow_run_id, runs server-side, suggests using get_status for follow-up. Does not explicitly exclude alternatives or mention prerequisites.

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