agy_security_audit

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states the tool scans for vulnerabilities but does not clarify whether files are modified, what the output looks like, or any permissions needed. The term 'audit' suggests read-only but is not explicit, leaving significant ambiguity.

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?

A single, direct sentence with no redundant wording. It effectively front-loads the core functionality and is appropriately sized for the tool's simplicity.

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 lack of output schema and annotations, the description is incomplete for confident tool invocation. It omits return format, the purpose of the 'model' parameter, and any side effects, leaving critical gaps for the agent to navigate.

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 coverage is only 50% (filesToAudit is described, model is not). The description adds no new meaning to filesToAudit beyond the schema and completely ignores the 'model' parameter, leaving the agent without guidance on how to use it.

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 uses a specific verb ('Perform') and identifies the resource ('target files'), with a clear scope: scanning for OWASP vulnerabilities and credential leaks. This distinguishes it from sibling tools like agy_analyze or agy_refactor, making its purpose unambiguous.

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 implies use for security auditing but provides no explicit when-to-use guidance or alternatives. It does not mention when to choose this over agy_analyze or other analysis tools, leaving the agent to infer the context.

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