Delimit Scan

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

The description claims this is a 'read-only scan' and 'Does not write to project files,' but the annotations declare readOnlyHint=false. This is a direct contradiction about a critical behavioral trait, so the score must be 1 despite the otherwise useful side-effect disclosure.

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 organized with labeled sections, opens with the one-sentence purpose, and has no filler. Every sentence contributes either routing guidance or behavioral context.

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 simple one-parameter tool with an output schema, the description covers what, when, when not, and side effects thoroughly. However, the conflict between the stated read-only behavior and readOnlyHint=false leaves a serious ambiguity about side effects, preventing a perfect score.

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%, and the single optional project_path parameter is already fully described with a default value and meaning. The description adds no parameter-specific detail, but none is required beyond what the schema provides.

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?

States a specific action ('Scan a project'), a clear object (the project), and the output ('report what Delimit can do for it'). It also lists concrete discovery results (OpenAPI specs, security issues, frameworks) and distinguishes itself from delimit_init and delimit_quickstart.

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?

Provides explicit 'When to use' and 'When NOT to use' guidance, naming delimit_quickstart and delimit_init as alternatives. The sibling contrast section further reinforces the correct selection logic.

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