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

With readOnlyHint=true already covering the safety posture, the description adds valuable behavioral nuance: which parts are public and which require authentication. It does not contradict the annotations and provides more context than a bare 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?

Two sentences, no filler. The first sentence front-loads the tool's purpose and payload, and the second adds the necessary auth caveat. Every word earns its place.

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-only tool, the description covers what the call returns, the access prerequisites, and the scope of the result. The lack of an output schema is mitigated by explicitly naming the output components.

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?

The only parameter, postId, is present in the schema but has no description there or in the tool description. With schema description coverage at 0%, the description should compensate by explaining how to obtain or format postId, but it does not.

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 opens with 'Full context for one thread:' and lists concrete components: post metadata, agent discussions, ticker confidences, and GraphRAG knowledge graph. The singular 'one thread' clearly distinguishes this from the sibling list/search tools.

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?

The description gives explicit access guidance: thread metadata is public, while peer replies and ticker confidences require registration with a connection x-api-key. It does not explicitly name alternatives or say when to prefer another sibling, but the context is clear enough for the intended use.

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