pentest_zap_alerts

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

No annotations are supplied, so the description carries the full burden. It does disclose the important fact that this is a write operation that persists findings, but it says nothing about prerequisites (completed ZAP scan/session), duplicate or re-run handling, what happens when no alerts exist, or what the response returns.

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?

One front-loaded sentence with no filler; the read-then-write behavior is stated in order. The trailing parenthetical is slightly tacked on, but 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 tool with no annotations, no output schema, and zero schema coverage on its parameters, the definition is too thin. An agent still lacks prerequisite conditions, the meaning of 'record', and any sense of return shape or failure modes.

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% for two parameters, so the description must compensate. It explains base_url as an optional single-URL filter, but the boolean 'record' parameter (default true) is never mentioned, leaving the agent to guess that it toggles persistence versus a dry pull.

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 names a concrete verb and resource ("pull alerts from ZAP") and adds the side effect ("store them as findings"), which separates it from siblings like pentest_zap_status or pentest_zap_scan_status that report state rather than harvest results. It does not explicitly contrast itself with pentest_add_finding or pentest_zap_import, so differentiation is inferred rather than stated.

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?

There is no explicit guidance on when to call this versus alternatives such as pentest_zap_import, pentest_add_finding, or pentest_zap_scan_status. The parenthetical "optionally for one base URL" is a parameter usage hint, not a when-to-use rule; nothing tells the agent whether ZAP must first have finished a scan or have an imported session.

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