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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered externally. The description adds only the content of the timeline, with no notes on pagination behavior, result ordering, or volume — acceptable but not rich.

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?

A single front-loaded sentence with no filler; the enumerated activity types are the only elaboration and each earns its place. Slightly longer than strictly necessary but well structured.

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?

No output schema, so the description carries some of the return-value burden and does list activity types, which helps. However it omits ordering, pagination semantics (cursor/limit), and whether the timeline is bounded — gaps an agent would face for a paginated aggregation call.

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% (contactId, limit, cursor, apiKey all documented), so the schema does the heavy lifting. The description adds no meaning about the required contactId or how pagination interacts with 'full timeline', leaving this at baseline.

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 (Get) and resource (a contact's full activity timeline) and enumerates the event types it aggregates. This distinguishes it as a composite per-contact aggregation tool rather than the narrower siblings like get_message_events or list_automation_enrollments, though it never names those alternatives.

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?

No indication of when to use this aggregate timeline versus the many narrower siblings (get_message_events, get_event_insights, list_automation_enrollments). The phrase 'full activity timeline' implies aggregate scope but gives no explicit when/when-not guidance.

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