spawn

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

With no annotations, the description properly discloses the key behavioral trait: the program is spawned in a suspended state (gated) for hook installation. It does not mention side effects, permissions, or return values, but the core behavior is transparent.

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?

A single sentence with no unnecessary words. It front-loads the key action and purpose, making it easy to scan.

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 simple spawn tool with 2 parameters and no output schema, the description covers the essential purpose. However, it lacks information about return values or process identification, which could be needed for subsequent actions like adding hooks.

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. However, it does not explain the 'program' parameter (e.g., path format) or the 'gated' boolean beyond implying suspension. Parameter meanings are left to inference from names and context.

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 action ('spawn a program'), the state ('suspended/gated'), and the purpose ('so hooks can be installed first'). It differentiates from sibling tools like 'attach' (attach to existing process) and 'resume' (resume suspended process).

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 implies usage before installing hooks, but does not explicitly state when not to use the tool or provide alternatives. The 'suspended' keyword hints that a 'resume' call is needed later, but this is not explicit.

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