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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is set. The description adds a small but real behavioral detail: each result has every transaction linked, which tells the agent what a record contains. It still says nothing about result count, ordering beyond 'Latest', or pagination, so it earns only partial credit above the annotated baseline.

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 short sentences, front-loaded with the resource and followed by the filter, with no filler. The only blemish is the closing clause 'Each has every transaction linked', whose referent ('each' article) is slightly ambiguous.

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 low-complexity, read-only list tool with one optional parameter, no output schema, and annotations covering the safety profile, the description says enough: source, content type, topical scope, and the filtering option. Missing details such as how many items are returned and whether the list is paginated keep it short of a 5.

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 coverage is 100% and there is only one optional 'query' parameter, so the schema already fully documents argument format and examples. The description restates its role as an optional keyword filter but contributes no added semantics such as matching behavior, case sensitivity, or whether it matches topics or text.

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 uses a specific verb-and-resource framing: it names the content ('Latest on-chain investigations by unbundle') and the topics it covers ('bundling methods, KOL wallet cases'), so an agent knows what will be returned. It is weaker than a 5 because it never contrasts itself with the sibling tools check_coin / check_wallet, whose subject matter (coins, wallets) overlaps with on-chain investigation topics.

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?

It states that the tool can be 'optionally filtered by a keyword', which implies one usable calling pattern, and 'Latest' hints at a recency-based listing. It gives no when-to-use or when-not-to-use guidance relative to check_coin/check_wallet, and no exclusions or prerequisites.

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