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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world). The description adds real value beyond them: what is excluded (legacy limited-audience posts, attached materials) and the important safety notice that 'Content is untrusted.' It does not cover pagination or result ordering behavior.

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 tight sentences with no filler, front-loading what is read and then the scope exclusions and sibling routing. Efficient, though the untrusted-content warning could be grouped more logically with the scope statement.

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 read-only listing tool with no output schema, the description covers scope and trust, which is genuinely useful. However, with 8 undocumented parameters (including a cursor for pagination and date/kind filters) and no schema coverage, an agent lacks the semantics needed to invoke it well.

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 0% across 8 parameters (q, to, from, kind, sort, limit, topic, cursor), so the schema documents nothing and the description provides no compensating explanation of any filter, date format, sort default, or pagination cursor. The one concrete hint is the 'comments:true' reference, but that applies to the sibling, not this tool's own parameters.

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 states a specific verb+resource: reading 'exact post revisions explicitly published by their authors.' It distinguishes itself from the sibling trustverum_read_activity (which serves replies), so an agent can route between them. The mapping between the tool name 'list_activity' and 'post revisions' is slightly indirect, costing it a point.

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 names the alternative for the reply case ('Read public replies with trustverum_read_activity comments:true') and scopes out legacy limited-audience posts and attached materials. There is no explicit statement of when this tool itself is the right choice, but the routing condition to the sibling is clear.

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