reverse_ensReverse-resolve an Ethereum address (0x…) to its primary ENS name and profile records. Keyless.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | An Ethereum address, e.g. "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide safety profile (readOnly, idempotent, not destructive). Description adds 'keyless' indicating no authentication needed, and mentions returning profile records. No contradiction.
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?
Extremely concise: two sentences, front-loaded with verb and resource, no wasted words.
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?
Tool is simple with 1 param and known return type (ENS name + profile). Description covers the purpose but lacks specifics on return structure or error handling. Adequate given 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?
Single parameter 'address' has full schema coverage (100%) and clear description in schema. Description adds no new information beyond what schema provides.
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?
Description specifies the verb 'reverse-resolve', the resource 'Ethereum address', and the result 'primary ENS name and profile records'. It clearly distinguishes from sibling 'resolve_ens' which likely does forward resolution.
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?
Mentions 'keyless' as a potential advantage, but does not state when to use or when not to use this tool versus alternatives like resolve_ens or other tools.
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.
Each tool has a clearly defined, distinct purpose. Even closely related tools like ask_pipeworx and ask_pipeworx_grounded are differentiated by use case (casual vs. high-stakes), and the prediction market tools each cover a specific function (research, edge detection, arbitrage, fill risk, tracking, cross-venue spreads). Detailed descriptions eliminate ambiguity.
Tool names predominantly follow a verb_noun pattern (e.g., ask_pipeworx, compare_entities, resolve_entity), but a few use noun_noun or adjective_noun forms (e.g., entity_profile, recent_alerts). The naming is generally predictable and readable, with minor deviations from a strict pattern.
The server offers 32 tools, which is above the typical 3-15 range for a well-scoped server. However, the vast domain (financials, prediction markets, news, memory, subscriptions, etc.) justifies the count. It is on the heavy side but still manageable with clear organization.
The tool surface is remarkably complete for the apparent domain: exploration (discover_tools, suggest_questions), identifier resolution (resolve_entity), data retrieval (ask_pipeworx, deep_research, entity_profile, compare_entities, recent_changes, validate_claim), prediction market analysis (full suite), memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), and extras (ENS, dependency scan, AI visibility). No obvious gaps exist.