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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds cursor-based pagination and the resume mechanism, which annotations do not convey, but it omits ordering, rate limits, and what the events represent.

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 that are front-loaded with the purpose, and the resume hint earns its place as operational guidance. It is slightly terse to the point of being cryptic about next_cursor's origin, but there is no wasted text.

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?

With no output schema, the description should explain the returned event stream and pagination fields, but it only alludes to next_cursor. For a simple read/list tool with full annotation coverage this is minimally adequate, not complete.

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 50% (company and environment are documented; after and limit are not). The description gestures at the cursor concept underlying the 'after' parameter but says nothing about 'limit' bounds or its effect, so it only partially compensates for the coverage gap and lands on the 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?

The description names a specific verb (Read) and resource (configuration and activity events) plus the mechanism (after a cursor), so the agent knows exactly what it retrieves. No sibling deals in events, so there is little to differentiate against, which is why this sits at a clear-but-not-sibling-scoped 4.

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?

'Resume from next_cursor' implies the pagination pattern, but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance. The agent is left to infer that this is a forward-scanning list call with no stated conditions for choosing it.

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