startup

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and the ordering requirement, but does not explain side effects, whether the call is idempotent, what happens if the agent is already started, or what the response contains. This is a significant gap for a state-changing startup operation.

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 a single sentence with a clear verb and a crucial usage note. Every word earns its place, with 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 the tool's simplicity (0 params) and the presence of an output schema, the description provides the key contextual information: it must be called first. However, it lacks details about idempotency and potential side effects, which slightly reduces completeness for an agent deciding how to handle repeated invocations.

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 input schema has zero parameters, and schema description coverage is effectively complete. Per the baseline for 0-parameter tools, the description need not add parameter details, and it doesn't need to compensate for missing schema information.

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 verb 'Start' with a specific resource 'openclaw-brain agent', clearly distinguishing it from sibling tools like 'shutdown' and other operational tools. The additional requirement 'Must be called before other tools' further defines its role as an initialization step.

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 explicitly states when to use this tool: before all other tools. This gives an unambiguous ordering constraint, even though it doesn't mention alternatives, the context is clear because startup is the prerequisite for everything else.

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