delimit_init

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

Lists side effects: creates .delimit/policies.yml, ledger dir, and optional settings.json, plus chmod operations. Also mentions no_permissions parameter to skip permission step. Since no annotations exist, the description fully covers behavioral traits.

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?

Well-structured with labeled sections, front-loaded key info, no wasted sentences.

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?

Covers purpose, usage, side effects, parameters, and sibling contrast. Output schema exists so return value explanation is optional. Complete for a one-time initialization tool.

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 100% so baseline is 3. The description adds context linking no_permissions to permission side effect, but doesn't add new meaning beyond schema descriptions for project_path and preset. Slight value uplift.

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 it initializes Delimit governance scaffolding, lists files created, and distinguishes from siblings by explicitly naming delimit_project_config and delimit_scan.

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?

Provides explicit 'when to use' (once per project, first time) and 'when NOT to use' (load config or discover capabilities), along with alternative tool names.

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