delimit_scan

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

No annotations are provided, so the description must disclose behavioral traits. It mentions scanning and analyzing but does not specify if the operation is read-only, whether it modifies the project, or any permissions needed. The agent cannot determine if this is a safe discovery action or if it has side effects.

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 extremely concise at two sentences, with the main action front-loaded. Every sentence adds value: first sentence states the core function, second sentence provides use case context and lists capabilities.

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, the description adequately explains the tool's purpose and what it analyzes. It covers key capabilities (OpenAPI, security, frameworks, tracking suggestions). A slight gap is the lack of clarity on whether the tool modifies the project, but overall complete for a discovery 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% as the only parameter (project_path) is fully described in the schema. The description adds no additional meaning to the parameter beyond what the schema provides, so 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 clearly states the verb 'Scan a project' and identifies the resource (project). It lists specific actions: finds OpenAPI specs, checks security issues, detects frameworks, suggests tracking. It distinguishes from siblings by labeling itself as a 'first-run discovery tool', which is unique among the many sibling tools.

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 explicitly states when to use: 'Use this when you first install Delimit or open a new project.' This provides clear usage context. However, it does not explicitly mention when not to use or provide alternative tools, though the context implies it's the initial discovery step.

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