delimit_scan

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

The description declares side effects: 'read-only scan via filesystem globs. Does not write to project files.' This fully discloses behavior. No annotations exist, so the description carries the burden and does it well.

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 well-structured with clear sections (purpose, when to use/not, sibling contrast, side effects). It is concise with no redundant sentences, front-loaded with the primary purpose.

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 single-parameter tool with output schema, the description covers discovery intent, output specifics, side effects, and usage context. No gaps remain; the tool is fully described for agent selection and invocation.

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 no extra meaning for the parameter beyond the schema's description and default. It does not elaborate on path format or constraints.

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 the tool scans a project and reports what Delimit can do, listing specific findings (OpenAPI specs, security issues, frameworks, tracking suggestions). It distinguishes from siblings delimit_quickstart and delimit_init by contrasting their purposes.

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 'When to use' and 'When NOT to use' sections provide clear guidance. It states when to use (first-run discovery on a new project) and when not (governance initialization or quickstart), with named alternatives.

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