delimit_security_scan

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

With no annotations and a sparse description, the tool's behavioral traits are undisclosed. It does not explain what the scan entails, whether it modifies anything, or details about the output, leaving the agent uncertain.

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 concise but under-specified. It consists of one short sentence that conveys the basic purpose but lacks necessary detail to be fully informative, balancing brevity with incompleteness.

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 complexity and many siblings, the description is too minimal. It fails to provide context about the scanning scope, output, or how it differs from similar tools, leaving gaps in understanding.

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 single parameter 'target' has a clear schema description ('Repository or file path.'), achieving 100% coverage. The tool description adds no extra meaning, so 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 'Scan for security vulnerabilities' clearly indicates the tool performs a security scan, but it is vague and does not distinguish from sibling tools like 'delimit_scan' or 'delimit_security_audit'. No specific resource or scope is mentioned, limiting its clarity.

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 no guidance on when to use this tool versus its many siblings, nor does it mention prerequisites or limitations. An agent would lack context to choose it appropriately.

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