pmg_quarantine_spamstatus

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

The description clearly labels the tool as READ-ONLY and indicates it returns a dict of summary counts. While no side effects are stated, the read-only nature is transparent. No annotations were provided to contradict.

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: two short sentences front-loaded with the key purpose and read-only flag. No unnecessary words or 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?

For a summary tool with an output schema, the description covers the essential points: purpose, read-only nature, configuration need, and alternative tool. Could expand on the returned dict structure but output schema likely covers that.

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 sole optional parameter (proximo_target) is fully documented in the input schema with a clear description. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 explicitly states 'get spam quarantine status summary', a specific verb and resource, and distinguishes itself from the sibling tool pmg_quarantine_spam which handles individual messages.

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 clear when-to-use guidance: for a summary use this tool, for individual messages use pmg_quarantine_spam instead. Also notes the configuration requirement.

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