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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the underlying endpoint (GET /events) and the definition of an activity; it says nothing about pagination behavior, result caps (limit max 100), or volume of returns, which a listing tool would benefit from disclosing.

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 short sentences, zero padding, with the resource definition front-loaded. The trailing 'GET /events' is endpoint trivia of marginal value, but it costs almost nothing.

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?

Reasonable for a low-complexity, zero-required-parameter read tool, and no output schema exists so return values need not be described. However, the description never addresses pagination or how results relate to the per-record activity listing sibling, leaving a modest gap for a tool whose schema is entirely pagination-focused.

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% with only two well-documented pagination parameters (limit, offset with next_offset guidance), so the schema carries the full burden. The description adds no meaning beyond it; baseline 3 is appropriate.

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 (List) and resource (activities), and enumerates the subtypes it covers (tasks, calls, appointments, notes), which removes ambiguity about what an 'activity' is. It scopes the operation to 'across the account' but never names or distinguishes itself from the closest siblings, teamgate_list_record_activities and teamgate_get_activity.

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?

'Across the account' implies an account-wide listing as opposed to the record-scoped sibling teamgate_list_record_activities, but the distinction is left for the agent to infer. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance.

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