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

The annotation already covers readOnlyHint, so the repeated 'READ-ONLY... changes nothing' is partly redundant. But the description adds genuine behavioral context beyond structured fields: it discloses that no matched text is published, that returned data is untrusted and citizen-authored, and that _meta carries a server-owned provenance boundary — meaningful trust/provenance disclosure an agent needs.

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?

Three sentences, front-loaded with the resource and content, then trust caveats, then read-only confirmation. Mostly earns its place, though the READ-ONLY sentence duplicates the readOnlyHint annotation.

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 return burden and does so reasonably: it names the notice categories and the trust/provenance posture. Pagination behavior of 'limit' is the only notable gap for a single-param read tool.

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 single parameter 'limit' has no schema description (0% coverage), and the description never mentions it, so it does not compensate. The name and min/max bounds make it a self-evident pagination cap, but no meaning about defaulting or behavior is added.

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 verb and resource with concrete content breakdown: 'Read public door-check telemetry: reader-safety notices, hygiene aggregates, and refusal counts.' This is far more informative than a tautology. It does not, however, explicitly distinguish itself from the many read-style siblings (payload_notices, porch_read, front_page), leaving that inference to the agent.

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 statement of when to use this tool versus alternatives like payload_notices or porch_read, and no exclusions or prerequisites. Usage is only implied by the word 'Read'. The agent gets no routing guidance.

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