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

Despite no annotations, the description fully discloses its non-authoritative nature, cache lag hours-to-days, that it reflects creates but NOT updates/deletes, and that it can return stale or deleted thoughts. This exceeds typical transparency and directly addresses the most important behavioral trait an agent needs to know.

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?

The description is compact and front-loaded with the purpose, followed by the critical warning and usage guidance. Every sentence adds value, with no fluff. The use of the warning symbol and clear formatting aids readability.

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?

Given the tool's complexity (cached layer, mutation caveats) and no annotations, the description is highly complete. It covers the key caveats, provides an upstream issue link, and clarifies when to use an alternative. Output schema exists, so return value details are not needed. This is a model description.

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 description coverage is 80%, so the schema already explains most parameters. The description adds nothing about individual parameters beyond the npub requirement for billing, which is also in the schema. It does not compensate for the one undocumented parameter (dpop_token), but since most are covered, the baseline 3 is appropriate.

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?

The description clearly states 'Get a thought's full connection graph' with a specific verb and resource. It distinguishes this from related tools by contrasting it with get_thought for verifying writes, and the 'full' qualifier implies the non-paginated variant. Sibling differentiation is implicit through the explicit warning against using it for recent writes and the reference to get_thought as authoritative.

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 explicit when-to-use and when-not-to-use guidance: 'Use this for fast traversal of established structure and for finding older thought IDs. Do NOT use it to verify a recent write — confirm mutations by ID with get_thought.' This names the alternative tool and the exact context where this tool is appropriate, which is exceptional.

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