checkov_scan

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

With no annotations, the description takes responsibility for behavioral disclosure. It states it scans local files only, requires no network access, and needs no allowlist check, signaling a safe, non-exfiltrating read operation. It also describes the return grouping, adding useful behavioral context.

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 sections for Args, Returns, and Note, each adding essential information without redundancy. It is concise and front-loaded with the primary purpose, making it easy to parse quickly.

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 the existence of an output schema, the description covers purpose, parameters, return values, and operational caveats like local-only scanning and no allowlist need. Minor omissions such as recursion behavior do not detract significantly from its usefulness.

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 schema has 0% description coverage, but the description fully compensates by explaining each parameter, including allowed framework values and example check IDs. This provides the semantic context the structured schema lacks, leaving no ambiguity about the arguments.

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 Infrastructure as Code for security misconfigurations using Checkov, which distinguishes it from sibling scanners focused on other targets. It lists supported frameworks, providing a precise scope and making the tool's use case immediately obvious.

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?

It provides clear context by enumerating supported IaC frameworks, implying this is the right tool for IaC security scans. However, it does not explicitly name alternative scanners or state when not to use it, so guidance is contextual but not comparative.

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