pmg_quarantine_blocklist_list

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

No annotations are provided, so the description carries full burden. It discloses that the operation reads data (no write), explains the pmail default behavior, and mentions the live-verified path. It does not discuss rate limits or permissions but is adequate for a read tool.

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 extremely concise with three sentences and a line about pmail. It is front-loaded with the main purpose and contains no redundant information. Every sentence adds value.

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's simplicity, the absence of annotations, and the presence of an output schema, the description is complete. It covers purpose, usage, param semantics, and a technical detail. No further information is needed for correct invocation.

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?

The description adds meaning beyond the schema: it explains that pmail scopes to one user, defaults to the authenticated user, and clarifies that an empty result means no entries for that user. For proximo_target, the schema already has a description, so no additional value needed.

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 'List PMG quarantine blocklist entries (read)', providing a specific verb and resource. It distinguishes from sibling tools like pmg_quarantine_blocklist_add and pmg_quarantine_blocklist_remove by explicitly noting the read nature.

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?

The description mentions optional pmail scoping and the requirement for PROXIMO_PMG_* config, giving context on when to use. It does not explicitly state when not to use or compare to other list tools, but the purpose is clear enough for selection.

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