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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is known. The description adds useful behavior context: it requires an API key, returns a structured object with listed fields, and relies on external sources (DeFiLlama + DexScreener). This goes beyond the annotations without contradicting them.

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 description is two sentences: the first defines the tool's scope, the second provides usage guidance, return shape, and a prerequisite (API key). Every sentence contributes, and the most important information is front-loaded.

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 with no output schema, the description covers the key aspects: what data it returns, when to use it, and what's required. It does not cover error/rate-limit behavior, but that is a minor gap for a simple forensics tool.

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%, with the query parameter fully described including examples. The description adds no additional parameter-level detail beyond what the schema provides; the baseline of 3 applies.

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 'Deep blockchain forensics' and enumerates specific capabilities (DEX pool health, TVL trends, token price behavior, whale flows), making the tool's function immediately clear. It also names its data sources (DeFiLlama + DexScreener), which distinguishes it from sibling tools like x711_price_feed and x711_wallet_investigate.

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 explicitly states when to use: 'Use before any DeFi transaction to assess real-time protocol health.' It does not mention exclusions or alternative tools by name, but it provides a clear deployment context that is sufficient for typical agent use.

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