Get Events

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: results are ordered and pagination is cursor-based. However, it says nothing about retention, whether the stream can be incomplete, how to resume or detect the end, or permission requirements — for a paginated read with zero annotation coverage, that leaves real gaps.

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 or repetition. It is efficient, though the extreme brevity leaves the remaining elements unaddressed rather than being purely a conciseness win.

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?

An output schema exists, so return-value explanation is not required, and parameter documentation is complete via the schema. Still missing is guidance on pagination continuation and end-of-stream detection, which matters for a cursor-paginated event tool.

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%, so the schema already documents limit, session_id, and since_sequence (including the inclusive-cursor semantics and the 200 cap), establishing the baseline of 3. The phrase 'cursor pagination' loosely ties to since_sequence/limit but adds no format or usage detail beyond the schema.

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 ('retrieves'), a specific resource ('ordered event stream'), and its scope ('for a session'), which distinguishes it from sibling session tools like get_session or read_session. It does not explicitly contrast itself with any sibling by name, so it falls just short of a 5.

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?

There is no statement of when to use this tool versus get_session, read_session, or get_job, nor any prerequisite or exclusion. The session-scoped event resource implies usage, but the agent is left to infer it entirely.

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