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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds genuine beyond-annotation context: first-page whole-window member counts with an equal-duration preceding comparison, and the paging invariant that retained paging requires unchanged filters, limit and List revision. It also explicitly disclaims side effects ('Does not change Lists or create alerts').

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-loaded with the 'Use when' trigger, then tightly sequenced: what it returns, the first-page comparison payload, the efficiency hint, the price-history pointer, the paging invariant, and the side-effect disclaimer. Dense but nearly every sentence carries decision-relevant information.

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 19-parameter tool with no output schema, the description does the important work of describing the distinctive return payload (member counts, preceding comparison, activity.comparisons) and the state invariants for paging. Remaining gaps are minor since the schema carries the per-parameter semantics at 79% coverage.

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 79%, so the schema already documents most parameters (mode, cursor, detail, order, date bounds). The description reinforces the paging contract ('unchanged filters, limit and List revision') but adds no syntax, format or constraint detail beyond what the schema states, which is the expected baseline here.

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 and resource: reviewing what changed among assets and Crypto Voices in a saved List, returning posts matching author OR asset members without duplication. It is clearly distinguishable from plain post search, though it never names the closest siblings (discover_activity, compare_activity) to sharpen the boundary.

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 opening clause gives explicit when-to-use context ('reviewing what changed... in a saved List') and routes away from adjacent work: 'Read price history separately as needed' and 'Use activity.comparisons rather than rereading every member.' No explicit when-not-to-use or named alternative tool, so it falls short of a 5.

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