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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about the cost ('0.01 USDC') and the backing source (Nansen Token Screener). However, it does not disclose response format, rate limits, or whether the operation is read-only. This is a moderate level of transparency.

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 three concise sentences that front-load the purpose, include concrete examples, and state the cost. Every sentence earns its place with no unnecessary fluff.

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?

Without an output schema or annotations, the description should explain what the user gets back and how this differs from sibling tools. It does not describe the response structure or clarify the 'holdings' aspect in the name. It is adequate for a simple screening tool but leaves notable gaps.

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 100%, so the baseline is 3. The description adds example natural-language queries that clarify the 'input' parameter, but it does not explain the relationship between 'input' and 'query' or between 'chain' and 'chains'. The added value over the schema is marginal.

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 action ('Screen tokens') and the resource ('Smart Money activity using Nansen Token Screener'). However, it does not explicitly distinguish this from the sibling tool 'nansen_smart_money_netflows', and the tool name 'holdings' is not directly explained. The core purpose is nevertheless clear.

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 provides natural language query examples ('what are whales buying on base?') that imply when the tool should be used. However, it does not explicitly contrast with alternatives or state when not to use it. The usage context is implied rather than explicitly guided.

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