spawn_getting_started

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

No annotations are provided, so the description carries full behavioral burden. It discloses that it 'reports what this project already has' and 'needs no credentials,' but does not explicitly state whether it modifies anything or describe the return format. The read-only implication is present but not explicit.

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 three-sentence description front-loads the critical 'START HERE' directive and efficiently enumerates workflow contents, project state reports, and credential requirements without redundant filler.

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 no output schema, the description partially compensates by listing the reported project artifacts (token, variant, game.json, docs) and the workflow steps covered. It lacks explicit return formatting, but for an orientation tool the provided context is largely sufficient for an agent to decide when and how to use it.

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 has 100% coverage; projectDir is fully described in the input schema. The description does not add parameter-specific meaning beyond mentioning 'project' context, so baseline 3 applies.

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?

Description explicitly states 'START HERE before any other spawn tool' and describes its function as 'The whole workflow in one call' plus reporting project state, distinguishing it from siblings like spawn_init and spawn_status.

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?

Explicitly instructs to use before any other spawn tool ('START HERE before any other spawn tool'), provides timing guidance ('before building anything visual'), and notes credential-free operation. The directive is clear even though alternatives are not named.

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