Open a story

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

With no annotations, the description carries the full burden and does well: it discloses the headless-browser execution, capture of events dispatched during rendering (e.g. connectedCallback), and the destructive act of clearing previously captured events. It does not cover failure modes (invalid storyId, load timeout) or whether it waits for render completion, so it falls short of a full 5.

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?

Front-loaded with the verb and resource, and every clause carries information (execution mode, capture timing, clearing, cursor), but the first sentence is dense with nested parentheticals that could be split for faster scanning.

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 usefully reports the sinceSeq cursor returned and states the ordering contract, which is what an agent needs to call this correctly. It stops short of describing error behavior or the lifecycle of the capture session, but the essentials are covered.

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?

Only one parameter and schema coverage is 100%, with the schema already documenting the storyId format and pointer to list_stories. The description's 'by id' adds no syntax or constraint beyond the schema, so the 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?

Starts with a specific verb+resource ('Load a story by id') and immediately qualifies the execution context (real headless browser) and the side effect of starting event capture. This differentiates it cleanly from siblings like get_events or list_stories, which operate on already-loaded data.

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 states the prerequisite ordering: 'Call this before click, dispatch_event, or get_events.' An agent knows exactly where this tool belongs in a workflow relative to its siblings.

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