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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds the ordering guarantee ('newest first'), which is genuinely useful behavior not in the annotations, but says nothing about pagination, truncation, or the result window.

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, zero filler, with the ordering guarantee front-loaded before the optional scope qualifier. Every clause earns its place.

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 read-only list tool with no output schema, the description conveys the entity types returned and their ordering. The main omission is pagination/windowing behavior, but the schema's limit parameter and annotations cover most of the remaining risk.

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 only 25% (just limit). The description compensates for the three ID parameters by explaining they scope the feed to one contact, company, or deal, but leaves open whether they can be combined and says nothing about limit semantics beyond what the schema states.

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 the resource (a unified recent-activity feed) and enumerates the event types it returns (texts, calls, emails, notes, deal stage changes, task completions). This implicitly distinguishes it from the per-type siblings (calls_list, sms_list, notes_list) as an aggregate view, though it never names them.

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?

Usage is implied by 'Recent activity' plus the optional scoping sentence, so an agent can infer it answers 'what has happened lately for this record'. There is no explicit when-to-use versus calls_list/sms_list/notes_list, and no stated exclusions or prerequisites.

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