pentest_zap_import

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

No annotations are provided, so the description carries the full burden. It discloses that alerts become findings (a mutation) but says nothing about deduplication, overwrite behavior, or what 'record' toggles despite that being a state-changing flag.

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 efficient sentence with the key action and format hint front-loaded; nothing is wasted.

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?

For a simple 2-parameter import tool with no output schema, the description covers the core action but leaves 'record' undocumented and gives no sense of what the tool returns or persists, which matters for a mutation.

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 0%. The description implies the path points to a ZAP JSON report, giving partial meaning for 'path', but it says nothing about 'record' (default true), which is the parameter most likely to change outcome significantly.

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?

States a specific verb (Import) and resource (ZAP JSON report) plus the follow-on effect (convert alerts into findings). This clearly separates it from pentest_zap_alerts and pentest_burp_import, though it never names an alternative explicitly.

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 parenthetical '(Report -> Generate -> JSON)' tells the agent how to produce the expected input in ZAP, and 'convert alerts into findings' implies it is the bridge from a ZAP scan to stored findings. However, there is no explicit when-to-use versus siblings like pentest_burp_import or pentest_zap_alerts, and no exclusions.

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