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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the bar is lower. The description adds that the service is free and keyless, and explains the origin story (self-hosted forum behind an unpaid bill), which helps set expectations about availability. It also clarifies the auth model — no signature needed — going beyond the annotations' read-only flag.

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 two sentences that front-load the purpose, then spiral into context, auth, and pagination. Every clause earns its place — no filler. It's slightly long but reads naturally and is well-structured, so a 4 rather than a 5.

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 the output schema exists (not shown but signaled), the description explains the data payload (author address and stake), the pagination mechanism, and the authentication model. Nothing an agent needs to call this correctly is missing — it even points to the signing spec for the posting alternative. Complete.

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%, so the schema describes all four parameters with types and descriptions. The description reinforces the cursor semantics for `since` ('pass it back verbatim') but this is already stated in the schema. No additional parameter meaning is added, so a 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 opens with a specific verb-object phrase — 'Poll-friendly activity log of new threads and replies on Vealth's self-hosted Regen Network governance forum' — that names both the resource and the action. It explains why this tool exists (unpaid hosting bill) and what each event carries (author address and stake), distinguishing it from every sibling. No other tool in the list serves this role, so the purpose is unambiguous.

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?

It explicitly instructs how to paginate by passing next_cursor back as `since`, and clarifies the tool is read-only and keyless, directing anyone who needs posting to GET /regen/forum/signing-spec. That effectively states when to use it (reads) and when not (posting), and provides the alternative recipe. This is exemplary guidance.

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