Export the event log

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces this with 'Changes nothing' and adds non-annotation behavior: output format, one event per line, and chronological ordering. It is silent on volume/size expectations for a full-log export, which is the main remaining behavioral unknown.

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 plus a routing clause; the output format and ordering come first, which is the most decision-relevant information. No filler.

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 carries the burden of describing the return value and does so precisely (JSON Lines, one whole event per line, oldest first). For a one-optional-parameter read tool with annotations, this is nearly complete; only expected output volume is missing.

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 100%, so the single checkpoint parameter is already fully documented. The description's 'everything, or only what happened since a checkpoint' restates the schema rather than adding format or semantics the schema lacks, so baseline 3 applies.

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 resource (the event log), the exact serialization (JSON Lines, one whole event per line), the ordering (oldest first), and the scope (whole log or since a checkpoint). It also names the sibling twin_changes so an agent can tell the two apart without opening either schema.

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?

Explicitly routes the agent to twin_changes when a one-line summary per event is wanted, which is the only realistic alternative among the siblings. It does not state when to prefer the checkpoint form over the full log, though the schema implies that trade-off.

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