pmg_quarantine_blocklist_remove

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

With no annotations provided, the description fully discloses behavior: low mutation severity, dry-run by default, confirmation to execute, no undo, config dependency, and output structure (PLAN vs status/result).

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 a single efficient paragraph that front-loads the key information (mutation, purpose, dry-run default). Every sentence adds value with no redundancy or filler.

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 tool has 4 parameters (1 required), an output schema, and a dry-run/confirm pattern, the description covers all necessary aspects: required config, parameter defaults, behavior, output, and error prevention (no undo). It is fully sufficient for an AI agent to use the tool correctly.

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%, but the description adds valuable context: pmail defaults to authenticated user, confirm toggles dry-run/execute, address is the email to remove, and proximo_target selects a specific target. It explains practical implications like no undo.

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 explicitly states 'remove an address from the quarantine blocklist' and labels it as a mutation, clearly distinguishing it from sibling tools like pmg_quarantine_blocklist_add and pmg_quarantine_blocklist_list.

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 specifies the default dry-run behavior, the need for confirm=True to execute, required config ('Needs PROXIMO_PMG_* config'), optional pmail scope, and the lack of undo with a suggestion to use pmg_quarantine_blocklist_add for re-adding.

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