pmg_quarantine_blocklist_add

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

No annotations provided, so description carries full burden. Discloses mutation type, dry-run behavior, and config requirement. Does not mention error handling, idempotency, or side effects beyond the API call.

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?

Description is relatively short and to the point. Uses two paragraphs but could be better organized. No unnecessary repetition.

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 no annotations and 4 parameters, description covers main purpose and critical behavior. However, it omits return value details, duplicate handling, and error scenarios. Output schema exists but not described.

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?

Description adds meaning for pmail (per-user scope) and confirm (dry-run vs execute). Address parameter lacks details but schema coverage is low (25%), and description partially compensates.

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?

Description clearly states verb 'add' and specific resource 'address to the quarantine blocklist'. It distinguishes from sibling tools like pmg_quarantine_blocklist_remove 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?

Description mentions dry-run default and confirm=True to execute, and needed config. Also notes pmail for per-user scoping. Lacks explicit when-not-to-use, but provides clear context.

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