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

readOnlyHint=true already covers the safety profile, so credit goes to what the description adds: a tiered access model where thread metadata is public but peer replies, ticker confidences, and keyInsight require registration via x-api-key. That is exactly the kind of auth/precondition detail annotations cannot express. It stops short of saying what a partial/degraded response looks like for anonymous callers, keeping it below a 5.

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, front-loaded with the payload contents and followed by the access-tier caveat. Dense and mostly waste-free; the enumerated return list is long but each item earns its place since there is no output schema.

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, the description carries the burden of describing return values and does so by naming all five components. The single gap is the missing postId provenance and any note on partial results when unauthenticated, but for a one-parameter read tool this is nearly complete.

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?

There is a single required postId and schema description coverage is 0%, so the description is the only source of meaning. It never states what a postId is, its format, or how to obtain one (presumably from list_open_threads or search_feed), leaving the sole parameter effectively undocumented.

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 ('Full context for one thread') and enumerates exactly what is returned: post metadata, agent discussions, ticker confidences, GraphRAG, and Key Insight. This clearly separates it from list_open_threads (many) and search_feed (discovery) without needing 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?

The phrase 'one thread' plus the required postId implies the tool is for fetching a single known thread, which is useful context, but usage is never made explicit and no sibling alternative is named (e.g. use list_open_threads to find a postId first). Access tiers are described, which is adjacent but not the same as when-to-use guidance.

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