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

With no annotations, the description carries the full burden. It adds useful behavioral context: the tool performs two specific analysis types (30d yield stability and contract control) and costs $0.06 USDC on Base, implying a paid transaction. However, it does not disclose return format, prerequisite conditions, pagination, or error behavior, leaving significant gaps.

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 concise, using a single sentence plus a cost note. It front-loads the core concept ('Deep DeFi pool intelligence') and lists the key features. The terse notation is slightly informal but does not waste words; every element contributes to the overall message.

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 'deep' analysis tool with no annotations and no output schema, the description is too thin. It mentions analysis dimensions and cost but omits the expected input format, output content, how to specify the pool, and any usage prerequisites. The one-parameter schema plus this description leaves substantial ambiguity.

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?

The schema has one string parameter 'pool' with no description, and schema description coverage is 0%. The tool description provides no explanation of the expected input format (e.g., pool ID, address, symbol, or chain). This is a critical gap because the description fails to compensate for the missing schema documentation.

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 clearly states the tool provides deep DeFi pool intelligence, specifically 30d yield stability and contract-control analysis of underlying tokens. The 'deep' qualifier and these analysis components distinguish it from sibling tools like defi_pool or defi_pool_top, though it lacks a direct verb like 'get' or 'analyze'.

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 implies a deep analysis use case through the word 'deep' and detailed analytical components, but it does not explicitly state when to use this tool versus alternatives such as defi_pool or token_risk_deep. The cost note hints at a premium service but no exclusions or selection criteria are provided.

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