Read the text of one node

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

Goes well beyond the readOnlyHint/idempotentHint annotations by disclosing that the first read freezes redacted text at capturedAt, later slices cannot splice a changing document, storage is bounded per observation, and continuations fail on expired observations, detached ids, navigation, or privacy-policy changes. This is rich, non-obvious behavioral detail an agent needs to use the tool correctly.

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 core read operation and budget, then proceeds through continuation mechanics, snapshot semantics, limits, and failure modes. Every sentence carries distinct information; there is no filler or repetition of annotation facts.

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?

Even without an output schema, the description enumerates all returned fields, explains truncation behavior, documents failure conditions, and covers pagination prerequisites. For a read/pagination tool this is unusually complete; an agent has what it needs to invoke initial reads and continuations safely.

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 80% and already describes offset, maxChars, sessionId, and observationId, so the baseline is 3. The description adds meaningful value: id targets a node/section, maxChars defaults to 600, offsets count JavaScript UTF-16 code units, and continuation includes sessionId. This strengthens understanding beyond the schema, though the schema still carries most parameter documentation.

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 verb ('Read') with a specific resource ('visible text of ONE node or section by id') and immediately differentiates itself as a single-node reader with bounded pagination. This clearly separates it from sibling tools like browser_find, browser_verify, or browser_scroll.

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?

Provides clear operational context: how to make an initial read, how to continue with continuation, and when offset requires observationId. It does not explicitly name alternative tools for finding or re-observing nodes, but it does instruct to 're-observe and re-find' for refresh, which gives practical guidance without exclusions.

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