Moralis MCP Server

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

With no annotations provided, the description carries full burden but only states the basic conversion function. It lacks disclosure of behavioral traits like rate limits, authentication needs, error handling for unregistered addresses, response format, or performance characteristics. The description doesn't contradict annotations, but provides minimal behavioral context.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every element ('Convert,' 'Ethereum address,' 'ENS domain,' 'if registered') earns its place, making it maximally concise while remaining 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?

For a single-parameter tool with no annotations and no output schema, the description covers the basic purpose adequately but lacks completeness regarding behavioral aspects and output details. It doesn't explain what happens when an address isn't registered or what the return format looks like, leaving gaps in contextual understanding.

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% with one parameter clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides (e.g., address format requirements, validation rules). Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Convert an Ethereum address') and target resource ('to its associated ENS domain'), with the conditional outcome ('if registered') providing precise scope. It effectively distinguishes from sibling tools like 'evm_resolveensdomain' which performs the reverse operation.

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 address-to-ENS resolution but doesn't explicitly state when to use this tool versus alternatives or provide any exclusions. The conditional 'if registered' hints at a limitation, but no explicit guidance on prerequisites or error cases is given.

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