get_suppression_log

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

No annotations are provided, so the description carries the full burden. It discloses that no API key is needed, describes the output structure in detail, and explains the meaning of suppression reasons and rate. It does not mention any potential side effects or rate limits, but the read-only nature is implied.

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 well-structured with clear sections for Args and Returns, and uses bullet points. Some phrasing, like 'discipline is the product', adds personality but does not harm conciseness. Slightly longer than strictly necessary but still efficient.

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 tool with one optional parameter and no output schema, the description covers the output fields, suppression reasons, and the significance of the suppression rate. It does not explicitly relate to sibling tools, but the context signals are informative enough.

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 explicitly defines the 'limit' parameter with its range (1–20) and default value (20), adding semantics beyond the schema which only specifies type and default. The schema description coverage is 0%, so this added value is essential.

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 the RefineX suppression log — a mix of delivered and suppressed signals' and explains what it shows, distinguishing it from sibling tools like get_live_signal and get_signals_summary.

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?

No guidance is provided on when to use this tool versus alternatives such as get_live_signal or list_signals. The only usage note is 'No API key required', but no comparative context.

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