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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety and repeatability are covered structurally. The description adds the result ordering ('newest first') and the composite nature of the feed, but says nothing about pagination behavior, result size caps, latency, or what happens when multiple scope filters are combined.

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?

Two sentences with zero redundancy: the first front-loads what the feed contains and its ordering, the second supplies the scoping constraint. Nothing is repeated from the title or annotations.

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 five-parameter read-only list tool with no output schema, the description covers content, ordering, and scoping well enough to call it correctly. The remaining gap is paging guidance (only hinted at inside the schema's limit/offset descriptions) and explicit sibling routing, which would matter given the many per-type list tools nearby.

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 only 40%: dealId, companyId, and contactId have no schema descriptions at all, and the description is what supplies their meaning as scoping filters for exactly one of those entities. The limit and offset parameters are already documented in the schema, so no credit is needed there, but the description carries the undocumented three.

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 resource (activity feed) with the enumeration of item types (texts, calls, emails, notes, deal stage changes, task completions) and sort order (newest first), which makes it clearly an aggregated cross-type feed rather than a single-type list. It does not explicitly name the sibling per-type lists (calls_list, notes_list, sms_list, tasks_list) it competes with, so differentiation is inferable rather than spelled out.

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 clause 'Optionally scoped to one contact, company or deal' implies a usage pattern (narrow the feed by entity), but there is no explicit statement of when to choose this over a per-type list like calls_list or notes_list. An agent must infer the choice from the word 'activity' alone.

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