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

Annotations already declare readOnlyHint and non-destructive, so the safety burden is light; the description still adds genuinely new behavior beyond them — owner-scoped visibility and the non-obvious fact that an unknown id yields an empty list rather than an error. It doesn't mention ordering, pagination, or result size, which would be the remaining useful disclosures.

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?

Three short sentences, each doing distinct work: purpose, exclusion, and behavior. Front-loaded correctly with the verb and scope first. The backticked tool names and the mid-sentence colon are slightly awkward but not wasteful.

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 single-parameter read tool with no output schema, this covers what to pass, what it returns conceptually (nodes), visibility scoping, and the error-free empty case. An agent could call it correctly from this text; only node ordering/shape remains unstated.

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 0% for the single parameter, so the description must carry it; it identifies conversation_id as the identifier of a previously captured conversation ("an earlier chat"), which is more than a bare string name. It stops short of describing the id's format or where to obtain it.

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 and resource ("List the nodes a captured conversation produced") scoped by conversation_id, and explicitly contrasts itself with `search` so an agent can discriminate it from siblings without opening the 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?

Gives an explicit use case ("to find what came out of an earlier chat") and an explicit anti-case ("Not for finding nodes by topic: search does that"), naming the alternative tool. Minor gap: it doesn't say what to do if you lack a conversation_id, e.g. how to discover one first.

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