pmg_statistics_spamscores

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

Labels as 'READ-ONLY' and describes return value, but without annotations the description carries full burden. No mention of authentication or side effects, but read-only is clearly indicated.

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?

Four sentences with no fluff. Front-loaded with 'READ-ONLY'. 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 output schema exists, description adequately explains return type and provides alternative tool. Parameter descriptions are complete. No gaps.

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 100% with all three parameters described. Description adds mapping 'start/end map to starttime/endtime' and clarifies they are optional Unix epoch timestamps.

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 'get PMG spam score distribution statistics' with optional time span, distinguishing it from pmg_quarantine_spam. The verb 'get' and resource are specific.

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 explicit alternative: 'For the raw quarantined spam messages use pmg_quarantine_spam instead.' Also notes required config 'Needs PROXIMO_PMG_* config.'

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