sns_reverseLookupReverse-lookup a Solana wallet address to its primary .sol domain name.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Base58 Solana wallet address |
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Primary .sol domain for the address | |
| address | Yes | The wallet address that was looked up |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. Description adds that it returns the 'primary' .sol domain name, implying potential multiple domains. Consistent with annotations.
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?
Single sentence that is clear and concise with no unnecessary words. Every part adds value.
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 lookup tool with one parameter and an output schema, the description is sufficient. It does not address edge cases like missing domains, but that is acceptable given the tool's simplicity.
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%, and parameter is described as 'Base58 Solana wallet address'. The tool description adds no further parameter semantics beyond the schema.
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?
Clearly states the action (reverse-lookup) and resource (Solana wallet address to .sol domain name). Distinguishes from sibling sns_resolve which is likely forward lookup.
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?
Description does not explicitly state when to use this tool versus alternatives like sns_resolve. While the name suggests reverse lookup, no guidance is provided for choosing between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but get_coin_intel and get_oracle_conviction overlap in providing intelligence signals; descriptions help differentiate but still may cause confusion.
Naming patterns are mixed: some use snake_case (get_bonding_curve), others use camelCase (sns_reverseLookup), and kol_leaderboard lacks a prefix that others like pumpfun_ have.
19 tools cover a broad range of pump.fun functionality, from token details to claims and social analysis; the count feels appropriate for the scope.
The tool set covers virtually all core aspects of pump.fun ecosystem: token info, intelligence, trading, claims, AMM quotes, metadata upload, SNS, and social sentiment, with no obvious gaps.