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

Annotations already cover read-only, idempotent, non-destructive, so the description's job is to add operational context — and it does: newest-first ordering, cursor-based pagination semantics, and a Free-workspace 90-day retention limit that materially changes what results the agent can expect. It does not describe rate limits or response envelope details, but for a read-only list that is a minor gap.

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?

Four sentences, each carrying distinct information: what it returns, how to filter, what an event looks like, how to paginate, and the retention constraint. The core identity is front-loaded and nothing is repeated from the schema verbatim.

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?

There is no output schema, so the description compensates by describing the event shape (eventKind values plus a raw payload) and the cursor/nextBefore paging contract, and it flags the 90-day data window. An agent has everything needed to call and page through it correctly.

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 baseline is 3; the description earns above baseline by explaining filter combination logic (entityType must pair with entityId; projectId and actorId are independent scopes) and by spelling out pagination flow, which the terse schema labels alone don't convey.

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?

States a specific verb and resource ("Read the workspace's activity feed") and disambiguates it from the rest of the catalog by defining it as the audit trail of who did what, ordered newest first. No sibling (get_task_status_history, list_comments) does the same thing, so an agent can select it confidently.

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?

Explicitly tells the agent how to narrow the feed: one entity via entityType+entityId, a whole project via projectId, or a person via actorId, plus the cursor rule (pass reply's nextBefore as before). It gives clear usage context but never names a sibling as a mutually exclusive alternative, so it stops 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.