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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description goes further by disclosing that the parallel 'agents' view counts documents deleted since, which contributors deliberately excludes, and by flagging names, titles, summaries and viewer text as untrusted content. Those are meaningful operational and security details beyond the annotations. It remains slightly thin on ordering/pagination behavior of the result set.

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?

Purpose is front-loaded in the first clause, which is good, but the remainder is a single dense run-on paragraph that mixes return-shape description, sibling comparison, parameter semantics and security warnings without structural separation. Every sentence carries information, yet the lack of breaks makes it harder to scan than it needs to be.

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 explaining the return shape and does so well (per-member counts, document counts, first/last activity). The untrusted-content warning covers a real risk for a report rendering user-authored names. The one gap is the unexplained 'agents' view, which is mentioned as if it were a parameter or sibling mode but appears nowhere in the schema.

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 baseline would be 3, but the description adds real meaning: it states docId OR shareId narrows to a single document (an either/or relationship the schema presents as two independent fields), restates 'since' windows with examples, and notes 'key' is the contributor id used by the activity feed's actor filter. The dangling 'key'/'url'/'agents' references, which are not schema parameters, slightly muddy the mapping.

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 first clause states a specific resource and scope: a ranked list of who replaced documents, with per-member counts and first/last timestamps. It also distinguishes its output from the activity feed's actor filter by explaining that 'key' is the same identifier that filter accepts. It does not, however, differentiate itself from close siblings like lnkdrp_get_activity or lnkdrp_list_revisions, so the sibling boundary is left to inference.

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 implies usage through the optional narrowing parameters (docId/shareId for one document, 'since' for a window) and explains the relationship to the activity log. But there is no explicit 'use this when / not when' guidance and no statement of which sibling to reach for when you want the raw event stream instead of contributor aggregates, so an agent must infer the choice against lnkdrp_get_activity.

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