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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no indication of result scope (all shared threads vs. the caller's), ranking, matching semantics, permissions, or rate limits. The phrase "shared knowledge" hints at breadth of corpus but leaves all operational behavior unstated.

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 single sentence wastes no words, but it is under-specified rather than concise — the brevity comes at the cost of any usable information. For a tool with zero annotation and zero schema-description support, this length is not appropriate.

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?

No annotations, no output schema, and an undocumented parameter mean the description is the only source of information, and it supplies effectively none. An agent could not reliably predict what this call returns or when it is the right choice.

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 one parameter (query) with 0% schema description coverage, so the description must compensate and does not. It says nothing about whether query is full-text, supports operators, or how an empty or broad query behaves.

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?

"Search shared knowledge" names a verb but not the actual resource: the tool operates on threads, yet the description never mentions threads or what corpus is being searched. It also fails to distinguish itself from the sibling list_threads or get_thread, so an agent cannot tell which retrieval tool to pick.

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 word "search" weakly implies query-driven retrieval versus creation, but there is no explicit statement of when to use this instead of list_threads, get_thread, or reply_to_thread. No prerequisites, no exclusions, no alternative routing.

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