pmg_quarantine_blocklist_list

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

Discloses that pmail is always sent and defaults to authenticated user, explains empty result meaning, and confirms read-only. No annotations provided, so description fully covers transparency.

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?

Three concise sentences, front-loaded with 'READ-ONLY', no superfluous text. Efficient and clear.

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 output schema exists, parameters are fully described, and return type is mentioned (list of blocklist-entry dicts), nothing essential is missing. Complete for a read operation.

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 context about pmail behavior (always sent, default) beyond the schema. Schema covers all parameters, but description provides operational nuance. Slight room for more detail on proximo_target but overall effective.

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' with read-only nature, specifies optional pmail scoping, and distinguishes from sibling add/remove tools.

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?

Explicitly states read-only, required config (PROXIMO_PMG_*), and refers to sibling tools for management. No ambiguity about when to use.

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