start

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

Beyond the annotations (readOnly=false, destructive=false), the description adds that it is a no-op in most deployments when already running, which is useful behavioral context. It does not contradict annotations; the idempotentHint=false is not violated by noting this deployment-specific behavior.

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 concise, front-loaded sentences. The first states the exact purpose, and the second adds valuable safety guidance without wasted words.

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?

For a zero-parameter tool with an output schema and existing annotations, the description covers the essential context: what it does, safety around idempotency, and a helpful pointer to `status` when uncertain. Nothing critical is missing.

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 tool has 0 parameters, so the description need not explain parameter semantics. The schema coverage is 100% with no properties, and the baseline for 0 params is 4.

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 'Start the Hermes agent' with a specific verb and resource. It implicitly differentiates from sibling tools like stop, restart, and status by focusing on the start action, and further clarifies its behavior when already running.

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 explicit guidance: it is safe to call when already running, most deployments treat it as a no-op, and advises checking `status` first if unsure. This tells the agent when to use the tool and when to check an alternative tool first.

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