delimit_quickstart

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

With no annotations provided, the description fully carries the burden. It discloses that the tool triggers init (writes .delimit/) and runs a scan (read-only), and detects the environment. This reveals both write and read side effects. It lacks details on auth or rate limits, but these are less critical for a quickstart tool.

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?

The description is very concise and well-structured with labeled sections for purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence adds value, and critical information is front-loaded.

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?

Given the tool's simplicity (single parameter with schema 100% coverage, output schema exists), the description is complete. It covers purpose, usage guidelines, side effects, and distinguishes from siblings. The agent has all necessary context to invoke the tool 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?

The only parameter, project_path, is fully documented in the schema with default and description (100% schema coverage). The tool description does not add meaningful semantics beyond the schema; it only implies the path is for the project to quickstart. Thus a baseline score of 3 is appropriate.

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 explicitly states the tool's purpose as a '60-second guided quickstart for a new install' that combines init, scan, and environment detection. It clearly distinguishes itself from sibling tools delimit_init, delimit_scan, and delimit_activate by contrasting their narrower scopes.

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 provides explicit 'When to use' (immediately after install) and 'When NOT to use' (for activation or diagnostics) guidance, and even names alternative tools delimit_activate and delimit_diagnose. This gives the agent clear decision criteria.

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