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

With no annotations provided, the description carries the disclosure burden. It meaningfully reveals append-only semantics, timeline ordering, and that the output is the raw log rather than a derived view. This is genuine behavioral context beyond what the schema or output schema would imply, though it does not mention pagination behavior.

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 short and front-loaded with the core purpose. The second sentence adds useful conceptual context ('the run is the event stream') but the parenthetical '#343 primary event stream' is slightly cryptic and could be clearer.

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 simple list operation with an output schema and only one required parameter, the description plus schema provides enough to call the tool correctly. It captures the essential identity of the tool and the read-only append-only nature, though it would benefit from explicit guidance vs sibling event tools.

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 only 33%, and the description adds no parameter detail. It does not clarify run_id format beyond the schema's 'Process run UUID', and limit/offset are not mentioned at all when they could have been briefly described.

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?

Description states a specific verb ('List'), a specific resource ('the event stream for a Process run'), and clarifies it is the primary/raw event stream. This meaningfully distinguishes it from generic siblings like event_list or process_run_get, even without naming them.

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 intended use is implied: call this to read the raw, append-only event log for a Process run. However, it does not explicitly state when to prefer this over alternatives such as event_list or process_run_get, and it gives no exclusions or prerequisites.

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