security_scan

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

No annotations provided, so the description must cover behavior. It mentions returning findings with details but does not explicitly state non-destructive nature or other behaviors like authentication. Adequate for a scanner.

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 with two sentences and an args line. Each sentence adds value: purpose, usage guidance, and parameter explanation. No wasted words.

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 a simple tool with one parameter and no output schema, the description covers what the tool does, what it returns, and the parameter. It could mention handling of invalid paths or empty results, but overall 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?

The single parameter 'path' is explained in the description: 'File or directory to scan (absolute, or relative to the project).' This adds crucial meaning beyond the schema's type-only definition. Schema coverage is 0%, so description fully compensates.

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 it scans Kotlin/JVM code for security issues, specifies a 216-rule analyzer, and lists what it returns. The verb 'scan' and resource 'Kotlin/JVM code' are specific.

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 usage context by saying 'Point this at a file or directory' and indicates it's intended for fixing issues while writing. No exclusions or alternatives are needed due to no siblings.

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