herdr_agent_start

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

With no annotations provided, the description carries the full burden. It discloses the main side effect (launching an agent), the return value, and a specific failure/retry behavior. However, it does not elaborate on what 'launch' entails (e.g., whether it blocks, if it mutates pane state) or describe the structure of the returned agent info.

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 three short sentences: purpose, return value, and retry caveat. Every sentence earns its place, with no filler, and the most important information (launch action) comes first.

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?

This tool has 5 parameters, no output schema, and no annotations, so the description needs to provide context. It covers the launch action and retry behavior, but does not mention prerequisites (e.g., needing an existing pane) or what to do after launch (e.g., using herdr_agent_prompt). The description is adequate but leaves several operational questions unanswered.

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 100%, so the baseline is 3. The description adds no extra parameter-specific meaning; the schema already documents each parameter and its constraints (e.g., timeout_ms range, kind='opencode').

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 uses the specific verb 'Launch' and identifies the resource as 'an opencode agent in a pane', clearly distinguishing this from sibling agent tools like herdr_agent_prompt or herdr_agent_get. It also explicitly states the immediate outcome: 'Returns agent info.'

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 provides practical retry guidance when the pane is not ready, but does not explicitly state when to use this tool versus alternatives such as herdr_agent_prompt or herdr_agent_get. It implies the usage context (you need a pane and want to start an agent) but lacks explicit exclusions or contrasts.

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