delimit_scan

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

No annotations provided, so the description carries the full burden. It discloses specific behaviors: scanning, discovering OpenAPI specs, security checks, framework detection, and tracking suggestions. However, it does not mention whether the tool is read-only or has performance implications.

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 sentences with purpose front-loaded. The second sentence repeats the first-run concept but adds value by listing specifics. Slightly redundant but overall efficient.

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 presence of an output schema, return values are not needed. The description covers what it does and when to use it. It lacks mention of prerequisites (e.g., valid project path) and could better distinguish from `delimit_init`, but is generally complete.

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% and the description does not add any detail about the `project_path` parameter beyond what is already in the schema. Baseline 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 states the verb 'scan' and resource 'project', and lists specific activities: finds OpenAPI specs, checks security, detects frameworks, suggests tracking. This clearly distinguishes it from sibling tools like `delimit_security_scan` or `delimit_repo_analyze`.

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?

Explicitly says 'Use this when you first install Delimit or open a new project,' providing clear context. However, it does not explicitly exclude use cases or mention alternative tools.

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