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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered; the description's 'Read-only' partly restates that. However it adds real context beyond annotations: the files are sourced from @idosgames/app-shell and must be written to the project root, and it clarifies the tool returns scaffolding rather than a mutation.

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?

Purpose is front-loaded and every clause is actionable, but the parenthetical file enumeration makes a single very dense sentence. It earns its length given the absence of an output schema, but could be split for readability.

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?

There is no output schema, yet the description fully describes the return contents and their origin, plus the required follow-up steps. For a zero-param scaffolding tool this covers everything an agent needs to invoke and act on it correctly.

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?

With zero parameters the baseline is 4. The description reinforces this by noting it 'takes no title_id', preempting an agent from trying to pass one, though no further parameter meaning is needed.

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?

States a specific verb+resource (get the host scaffold) and enumerates exactly what the scaffold contains (index.html, main.tsx, app.config.ts, wallet files, modules.ts, config). It clearly distinguishes itself from get_module and get_manifest by positioning itself as the starting base that those build upon.

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 scopes usage to NEW projects and lays out the ordered workflow: write files to root, install versions from get_manifest, then add modules with get_module. It even explains the selection rule for modules (systems with inBase, games with the modules each game 'uses'). Alternatives and sequencing are fully specified.

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