Delimit Quickstart

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

Annotations only provide readOnlyHint=false and destructiveHint=false; the description adds concrete side effects: it triggers init (writes .delimit/) and runs a read-only scan. This is valuable behavioral context beyond the annotations, though it does not go deeper into failure modes or environmental interactions.

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?

Each section—summary, when to use, when not to use, sibling contrast, side effects—adds distinct value and is front-loaded with the core purpose. No filler or redundant restatement of the schema.

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?

The description fully orients an agent: when to call, when not to, which siblings do what, and what side effects to expect. With the output schema and full parameter schema present, nothing needed for correct invocation is missing.

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% with the single project_path parameter fully described (default '.'). The tool description adds no extra parameter semantics, aligning with the baseline 3 when the schema carries the weight.

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 names a specific outcome ('60-second guided quickstart for a new install') and clarifies it as the unified first-run flow combining init, scan, and environment detection. It explicitly contrasts with delimit_init, delimit_scan, and delimit_activate, so an agent can distinguish it without inspecting schemas.

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?

A 'When to use' section defines the exact trigger (immediately after installation) and the 'When NOT to use' section routes to delimit_activate and delimit_diagnose. The sibling contrast further clarifies the alternatives, leaving no ambiguity about when to select this tool.

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