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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context by disclosing cursor-based pagination and the next_cursor continuation token. It does not say anything about event ordering, delivery guarantees, retention window, or what an event object contains.

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, front-loaded with the verb and resource, with no filler. The pagination sentence is terse to the point of ambiguity — it does not say whether next_cursor is an input or a returned value — which costs a point.

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 four-parameter read tool with no output schema, the description covers purpose and pagination but leaves the return payload unexplained (what an event looks like, its ordering, whether the stream is bounded). It is adequate to invoke the tool, but not complete enough to help an agent reason about what it will get back.

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 50% — company and environment are documented in the schema, while `after` and `limit` are not. 'After a cursor' plus 'pagination uses next_cursor' does convey that `after` takes a cursor token, but the format (numeric string per the pattern), the meaning of `limit` beyond its max of 200, and how next_cursor feeds back into `after` are left implicit.

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 (read) and two concrete resources (configuration and activity events) with a scope qualifier (after a cursor). No sibling in the provided list covers event streams, so the differentiation is implicit but clear; the description stops short of naming anything it is contrasted with.

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 cursor framing implies an incremental polling / sync use case and the second sentence signals how to continue, which is implied usage rather than stated guidance. There is no explicit 'use this when...' clause, no mention of when not to use it, and no alternative named.

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