pmg_quarantine_blocklist_remove

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

Discloses mutation with low risk, dry-run safeguard, and authentication/config prerequisite. Without annotations, it adds necessary behavioral context beyond the schema.

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 compact sentences plus a technical note; no fluff. The information is front-loaded, but the API path detail could be considered unnecessary for most agents.

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?

Covers essential aspects: action, safety (dry-run), config requirement, and parameter scope. With an output schema present, return values are omitted. Could include error behavior but still adequate.

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?

Adds meaning for pmail (per-user scope, default to authenticated user) and confirms role (executes after dry-run). Schema coverage is low (25%), so description compensates partially, but address is self-explanatory.

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 verb 'remove' and the resource 'address from the quarantine blocklist', distinguishing it from sibling tools like add and 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?

Provides explicit behavior: dry-run default, confirm=True to execute, and config requirement. However, it does not explicitly contrast with sibling tools, though the name makes it clear.

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