pmg_spam_config

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

No annotations are provided, so the description must carry the full burden. It declares the tool as READ-ONLY and mentions required configuration, but does not elaborate on potential side effects or rate limits. Given the read-only nature, this is largely sufficient, though additional details on response format (beyond output schema) could enhance 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?

The description is very concise, with two front-loaded sentences. 'READ-ONLY' is placed at the beginning for immediate clarity. Every sentence adds value, and there is no redundant information.

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 simple read-only configuration retrieval tool, the description is complete. It explains the return value (a dict of settings) and mentions key data elements (score thresholds, toggles). The existence of an output schema further reduces the need for additional details.

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 input schema covers both parameters with 100% coverage, including descriptions. The tool description does not add additional semantic meaning beyond what the schema provides. Baseline 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 clearly states the tool is READ-ONLY and retrieves PMG spam filter configuration. It explicitly names the resource and the action ('get PMG spam filter configuration'), and distinguishes itself from its sibling pmg_spam_config_update by mentioning it for changes.

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 explicitly says when to use this tool (to view config) and when to use the alternative (pmg_spam_config_update for changes). It also mentions a prerequisite ('Needs PROXIMO_PMG_* config'), providing clear usage context.

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