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

With no annotations, the description carries the burden of explaining behavior. It explicitly states the operation (resolving a name/address) and lists the returned data fields, which conveys the read-only nature. It does not cover error handling or edge cases, but for a straightforward lookup this is reasonable.

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 three concise sentences: a purpose, a returns list, and a contextual framing. It is front-loaded with the main verb and resource, and no sentence is redundant or wasted.

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 lookup with no output schema, the description gives a solid overview of the operation and return data, plus the broader 'social identity layer' context. It could be more complete by mentioning error behavior or an example, but overall it is adequate for typical use.

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%, and the param description already documents the format (wallet address or .mega name). The tool description's phrase 'wallet address or .mega name' adds no new meaning beyond the schema, so the baseline 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 clearly states a specific verb ('Resolve') and resource ('wallet address or .mega name' into an identity profile), and lists concrete return fields. It positions the tool as the 'social identity layer' which conceptually distinguishes it from siblings, but it does not explicitly compare against sibling tools, so it falls short of a 5.

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 this is the go-to for identity resolution and frames it as the 'social identity layer for MegaETH,' suggesting when it is appropriate. However, it does not explicitly name alternatives or state when not to use it, leaving the differentiation to the reader.

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