pmg_quarantine_virus

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

No annotations provided, so the description carries full burden. It discloses the read nature, default behavior for pmail, and mapping of start/end to query params. This is sufficient for a read-only list operation.

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 concise, with no redundant information. It front-loads the purpose and then provides technical details in an efficient manner.

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 an output schema and 4 optional parameters, the description covers prerequisites, parameter behaviors, and the API path. It is complete for a list 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?

Schema coverage is 25% (only proximo_target described). The description adds meaning for pmail (per-user scope, default to authenticated user) and start/end (Unix epoch mapping). This adds value beyond the schema.

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 it lists virus quarantine entries (read) and specifies the API path. Among siblings like pmg_quarantine_spam and pmg_quarantine_virusstatus, it distinguishes itself as a list operation for virus quarantine.

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 mentions the prerequisite 'Needs PROXIMO_PMG_* config' and explains the pmail scope. While it doesn't explicitly list when to use alternatives, the context of 'virus' vs siblings like 'spam' provides implicit guidance.

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