kickstart_service

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

No annotations are present, so the description carries the behavioral disclosure burden. It explicitly discloses that kill_existing=true passes -k and kills a running instance first, which is the main side-effect. It does not mention permission requirements or what happens when the service is not loaded, but the destructive behavior is surfaced.

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 short and front-loaded with the primary action before the argument explanations. There is no filler, repetition of the schema, or unnecessary detail.

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 two-parameter tool with an output schema, the description covers the action and both parameters well. It omits prerequisites such as the service needing to be loaded before kickstart versus bootstrap, but this is a minor gap for a relatively simple tool.

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 compensate, and it does. The Args section explains target with a concrete launchd example and explains kill_existing's exact effect via -k. This adds meaningful semantics beyond the raw schema's titles and types.

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 opens with 'Start or restart a service via launchctl kickstart', which is a specific verb and resource. It clearly distinguishes this tool from sibling operations like bootstrap_service, bootout_service, enable_service, and disable_service by naming the exact launchctl action.

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 states the core operation ('start or restart') but does not explicitly say when to choose kickstart_service over bootstrap_service or bootout_service, nor does it mention exclusions. Usage context is implied by the operation and sibling names, but no direct guidance is provided.

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