layerfs_project_init

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

Goes well beyond annotations: discloses platform requirement (Linux), a native addon dependency, one-time semantics (consistent with idempotentHint=false), and that it is never invoked automatically. Still silent on failure behavior, what state the project ends up in, and whether re-invocation errors out.

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?

Three short sentences, front-loaded with the action, then constraints. No filler; every clause carries actionable information.

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?

No output schema and no description of the resulting state, so the agent doesn't know what to check afterward or how this relates to layerfs_project_list_branches / layerfs_status. Prerequisites are covered, but the post-condition and error surface are not.

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 coverage is 0% and the single parameter sourcePath is undocumented in the schema. The description partially compensates by saying it comes 'from a host directory', which implies a host filesystem path rather than a workspace path, but adds nothing about absolute-path requirements or path resolution.

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 and resource: 'Initialize this server's project from a host directory', and 'one-time import' clarifies the nature of the operation. No sibling performs project initialization, so it is distinguishable, though it never explicitly contrasts with layerfs_workspace_mount or layerfs_project_list_branches.

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?

'Explicit, one-time import' and 'Never called automatically' give clear when-to-use framing plus a when-not (don't invoke implicitly). It stops short of naming alternatives or stating what to do if a project already exists, so it stops below a 5.

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