enhanced_scan_directory

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool performs a scan with monitoring, but does not mention whether it modifies files, requires authentication (despite having a 'user_token' parameter), or any side effects. Critical behavioral context is missing.

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 a single, front-loaded sentence that conveys the core functionality. It is concise but could be restructured to include more detail without becoming verbose.

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?

With 5 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain what 'comprehensive' and 'multi-tool' entail, the monitoring lifecycle, or the output format. Sibling tools like 'scan_directory' suggest a simpler variant, but no differentiation is provided.

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 covers all 5 parameters with descriptions, so baseline is 3. The tool description does not add additional meaning or context beyond the schema, such as clarifying the relationship between 'enableMonitoring' and 'schedule', or the expected format of 'policies'.

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 action ('Perform comprehensive multi-tool SAST scan') and the resource ('directory'), and highlights the key differentiator ('continuous monitoring option'). This distinguishes it from sibling tools like 'scan_directory'. However, it could be more specific about what 'multi-tool' means.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The description does not contrast with sibling tools or specify prerequisites. The only implicit guidance is the 'continuous monitoring' option, but no alternatives are mentioned.

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