gameforge_init_project

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

With no annotations, the description carries the full burden; it does disclose the concrete write side effects (creates standard asset directories and gameforge.project.json) and the 'update' mode. It does not say whether re-running overwrites existing manifest/directory contents, whether it fails if the directory already exists, or what the tool returns.

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 sentences, verb-first and front-loaded, with no filler. The preset enumeration is long but earns its place by mapping enum values to recognizable camera styles.

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 seven-parameter mutation tool with no annotations and no output schema, the description covers the core action and created artifacts but omits idempotency/overwrite semantics, error conditions, and return value. Enough to call it, not enough to call it confidently in a pipeline.

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 100%, so the schema already documents all seven parameters and three enums, establishing a baseline of 3. The description adds modest value by naming the real-world camera presets that map to the genre_preset enum values, but says nothing about workspace_dir, target_engine, or the override parameters.

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: initialize/update a deterministic game project in the 'SQLite Style Vault'. It also enumerates the camera-math presets, which helps distinguish it from style-bible and export siblings. The only fuzziness is what 'SQLite Style Vault' and 'deterministic' operationally mean, and 'or update' leaves the exact lifecycle role slightly ambiguous.

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 a setup step (it creates directories and the project manifest), but it never says this must be called before the sibling generation/export tools, nor when to re-run it versus leaving the project alone. No alternatives or exclusions are named, so the agent must infer ordering from the tool name alone.

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