why

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

No annotations are provided, so the description carries the full burden. It discloses the read nature (verb "Reads") and a genuine output behavior (direct read for a single chain, triage list for several), but omits permissions, side effects, pagination, and any explicit read-only declaration.

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-loads purpose after a short rhetorical hook, then covers usage and the replaced tools in a compact block. Every sentence carries information, though the opening "Why is this here?" is stylistic rather than substantive.

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 and no annotations, the description adequately covers the primary (required) `name` parameter's dual behavior and the read/triage semantics. The unexplained optional `initiative` parameter is the main residual gap.

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 50%: `name` is documented in the schema and the description largely restates it (chain vs node), while the optional `initiative` parameter is undocumented in both places. The description adds the ordered-steps/triage nuance but does not compensate for the gap on `initiative`.

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 concrete verb and resource: "Reads the saved reasoning that leads to a node" and the state → reasoning → decision trail, explicitly distinguishing it from reading "an isolated record." It does not, however, distinguish itself from near-siblings like `chain` or `trace`, so an agent must still infer the boundary.

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?

Gives explicit operating modes: pass a chain to read its ordered steps, or any node to see the chain it belongs to, with single-vs-multiple handling described ("read directly when there is only one, listed for triage when there are several"). It stops short of naming which sibling to use instead when a caller wants something else.

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