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

With no annotations provided, the description carries the full burden of disclosing behavior. It transparently states that the tool returns balances, activity, labels, and a score, and that multichain lookup is supported. However, it does not mention potential caveats such as data freshness, support for unsupported chains, or whether the operation is strictly read-only, though the 'get_*' prefix makes mutation unlikely.

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 consists of two short sentences with no filler. It front-loads the core purpose and data scope, then adds a single useful capability note. Every phrase contributes meaning, and the structure is easy for an agent to parse quickly.

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 read-only tool with two parameters and no output schema, the description is largely complete: it names the resource, the data categories returned, and a key capability (multichain). It does not explicitly describe the return format, error cases, or chain limitations, but the absence of an output schema makes this less critical, and the given details suffice for basic invocation.

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 both address and multichain are already documented. The description's 'Supports multichain lookup' merely restates the schema's multichain semantics without adding format details, constraints, or behavioral nuances beyond what the schema provides, so the baseline score 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 begins with a precise verb-resource pairing: 'Wallet intelligence for a specific address,' which clearly identifies the tool's focus. It lists concrete data types returned (balances, recent activity, labels, smart-money score), making it easy to distinguish from siblings like get_market_overview or get_whale_movements, which are not address-specific.

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 usage for retrieving wallet-level intelligence, but it does not explicitly state when to choose this tool over alternatives or provide exclusions. Sibling tools like get_smart_money and get_whale_movements could overlap conceptually, but no routing guidance is offered, so agents must infer the boundary from the address-specific phrasing.

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