timps_container_image_scanner

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

Without annotations, the description carries the disclosure burden. It does reveal a key behavioral trait: it wraps installed tools and falls back to static Dockerfile analysis. However, it does not describe side effects, execution duration, environment requirements, or what the results look like—meaningful gaps for a tool with no annotations.

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 two tightly written sentences. The first sentence states purpose and outputs, the second explains implementation and fallback behavior. Every word contributes value; no fluff or repetition.

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?

The tool wraps multiple scanners and has no output schema, so the description should clarify what the agent should expect in return. It explains scanning scope and fallback, but leaves out how the 'request' parameter steers the scan, what result format is returned, and whether the scan targets a local image, registry image, or a Dockerfile path. These gaps make it adequate but not complete for a tool of this complexity.

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 description coverage is 100% for both parameters ('request' and 'language'), so the schema carries the parameter meaning. The description adds no additional parameter context or usage examples, which is expected at this baseline.

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 states a specific action ('Scan') with a specific resource ('container image / Dockerfile') and the exact value produced ('CVEs, misconfigurations, and supply-chain risk'). It also explains the implementation approach (wrapping trivy/grype/syft with a static analysis fallback), making the tool's role clear and distinct from generic security tools.

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?

Usage context is implied by the scope: use when you need vulnerability or risk scanning for container images/Dockerfiles. However, there is no explicit guidance on when NOT to use it or which sibling tools (e.g., security_guard, sbom_generator, license_compliance_scanner) would be better alternatives for adjacent use cases.

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