events

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

With no annotations provided, the description carries the full burden. It usefully discloses that the operation is read-only, returns paged data, and times out after 90 seconds. However, it does not describe pagination mechanics, error behavior, or how the timeout manifests, leaving meaningful 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?

The description is one compact sentence with the core purpose front-loaded and only one extra behavioral fact (90-second timeout). Every word earns its place, despite the minor punctuation issue in the second clause.

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?

This tool has 17 parameters, no required fields, no output schema, and no annotations, so the single-sentence description is insufficient. Missing context includes how to page through results, what the default response shape is, which selector (session, udid, leaseId, runId) should be preferred, and what 'daemon-owned session event timeline' implies operationally.

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 high at 88%, so the schema already documents most parameters and the baseline is 3. The description adds the 'paged' hint, which gives some context for the undocumented limit and cursor parameters, but it does not explain how to use them for pagination.

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 uses a specific verb ('Read') and names a distinct resource ('daemon-owned session event timeline'), with 'paged JSON-friendly entries' clarifying the output style. It is clear about the tool's basic function, though it does not explicitly differentiate it from sibling tools like logs or session.

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 guidance about when to use this tool versus alternatives such as logs, session, or get. The description says what the tool reads but gives no context about selecting a session, lease, or run versus relying on defaults.

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