gerenciar_allowlist

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

With no annotations, the description carries the transparency burden. It discloses that the tool manages the allowlist and is a mandatory prerequisite for scans, which is critical behavioral context. However, it does not explicitly mention side effects of add/remove (e.g., whether removal invalidates ongoing scans), but the action parameter covers the basic operations. No contradictions.

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?

Two sentences, front-loaded with the core purpose and immediately followed by the crucial usage constraint. No filler or redundancy—every word earns its place.

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 is simple (3 params, 1 required). Given the high schema description coverage, an output schema (indicated), and the clear prerequisite message, the description fully contextualizes when and why to use it. No gaps remain.

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 100% with descriptions for all parameters, so the baseline is 3. The description adds value by giving an example for the 'note' parameter (context of authorization) and emphasizing the critical role of the 'entry' parameter. It provides practical guidance beyond the schema's raw types.

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 tool manages the allowlist of authorized targets, using the specific verb 'gerencia' and the resource 'allowlist de alvos autorizados'. It distinguishes itself from sibling scanning tools by emphasizing that no scan tool will work without the target being in the allowlist, making its unique purpose explicit.

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?

It explicitly states when to use: 'Configure sempre antes de iniciar um pentest' and warns that no scan tool will function without the target being here. This gives clear preconditions and prerequisites, and by implication tells the agent to use this before any scanning tool, effectively excluding alternatives.

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