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

'Overview' hints at a read-only operation, but the description does not disclose side effects, authentication requirements, or whether calls are destructive. The phrase 'per signed wallet' raises more questions than it answers.

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 short but includes irrelevant promotional content about free trial calls. This distracts from the tool's actual functionality and makes the description less clear.

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?

The description omits expected return values, use cases, and any operational details. It is not sufficient for an agent to understand what the tool does or when to invoke it.

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?

Both parameters are string fields with generic descriptions ('Wallet to process' and 'Address to process') that do not clarify the difference between them. No format, purpose, or relationship is explained.

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 says 'wallet overview' but never explicitly states what information is returned or what action is performed. The trial-call marketing note does not clarify the tool's core purpose.

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?

There is no guidance on when to use this tool versus the many sibling wallet-related tools like wallet-activity, wallet-balance, or wallet-scan. The description gives no context for selection.

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