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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses that the data is untrusted citizen-authored content, that a server-owned provenance boundary rides on CallToolResult _meta, and that the call is idempotent ('can be repeated safely'). The READ-ONLY restatement is redundant, but the provenance and trust caveats are meaningful.

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?

Front-loads what the tool is before the caveats, and each sentence contributes something (scope, safety, verification routing, provenance). Dense with domain jargon but no wasted filler.

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?

With no output schema, the description carries the burden of describing the return and does so reasonably: rows are untrusted address-like payloads from the gate's log, with a provenance boundary in _meta. Combined with the annotation and full param coverage, an agent has enough to call it correctly, though pagination/row-shape detail is absent.

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 description coverage is 100% and the single `limit` parameter is fully documented in the schema (default 50, max 200). The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific resource (the payload gate's public log) and its exact scope: every write carrying an address-like payload not on /api/official. It also routes the agent toward the `official` tool for verification. It does not, however, differentiate itself from the similarly-named sibling `screen_notices`, leaving one ambiguity.

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 implies usage ('check any payload against the official tool before trusting it') but frames it as a post-read caution rather than an explicit when-to-invoke rule. There is no statement of when this tool should be preferred over alternatives such as screen_notices or official.

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