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

No annotations are supplied, so the description carries the full burden. It discloses neither the result shape (messages vs. profiles vs. channels), nor matching semantics (exact vs. partial address match), nor pagination/result-limit behavior, nor any permission or rate-limit constraints. The appended '200 Successful Response' HTTP boilerplate adds no behavioral information.

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 two substantive sentences are front-loaded and contain no filler, but the trailing HTTP status block ('200: Successful Response, Content-Type: application/json') is leaked API-spec boilerplate that does not earn its place. The useful content is very short relative to what the tool needs.

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 simple two-required-parameter search this is roughly adequate, but with no annotations and no output schema the agent receives no information about what a hit looks like or how results are paged. The three optional parameters are left entirely unexplained.

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 67%, and the description adds no parameter meaning at all. The two undocumented parameters (page, page_size) get no explanation, and 'chain' is described only as 'Blockchain' with no enumeration of accepted values, which matters because chain and address are required and a wrong chain silently changes results.

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 names a specific verb and resource ('Search IM database for a cryptocurrency wallet address') and scopes the surface ('mentions in Telegram, Discord or other chats'), which separates it from sibling lookups like search_im_messages or get_documents_by_wallet. It does not explicitly distinguish itself from search_leaks_by_wallet, the closest ambiguous alternative, so it falls short of a 5.

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 'Find mentions in Telegram, Discord or other chats' implies the use case (locating wallet address references in chat logs), but there is no explicit when-to-use, when-not-to-use, or named alternative such as search_leaks_by_wallet. Guidance is inferable but not stated.

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