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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds real behavior: a page may be short of limit when events are large, the cursor loop terminates on null nextCursor, and a purged artifact subject returns id null while its title is retained. It stops short of describing retention windows or authorization scope in detail.

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 core read statement and then pagination before subject nuance. The middle sentence is dense but every clause carries operational information; the parenthetical about purged artifacts borders on over-detail but is genuinely non-obvious.

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 an output schema present, the description doesn't need to explain return shapes, and it covers the two things an agent would otherwise get wrong: short pages and the cursor loop, plus the subject edge case. It omits filter-combination semantics and any note on authorization/visibility limits of team feeds.

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 100%, so each of the 7 parameters is already documented, which sets the baseline at 3. The description only adds marginal meaning beyond the schema for subject (the purged-artifact id-null case); team/type/actor/since/limit are simply restated or left to the schema.

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 concrete verb+resource ('Read authorized personal or team activity') and names the pagination and attribution model, so the tool's identity is unambiguous. It does not explicitly distinguish itself from adjacent read tools in the sibling list (connection_audit_recent, workspace_changes, notification_mailbox), which keeps it short of a 5.

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 gives actionable in-tool guidance for paging ('while nextCursor is not null, call again with cursor: nextCursor') and explains how to narrow with subject. However, it never states when to prefer this over auditing/changes/notification siblings, so alternative selection is left to inference.

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