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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description adds value by disclosing the shape of the payload (owner, expiry, chain addresses), which is real behavioral context beyond the annotations. It does not cover error behavior for unregistered names or explain the unusual idempotentHint=false, so it stays at a solid 3.

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?

Two short sentences, front-loaded with the return payload. The second sentence defining THORNames is mild but useful domain context for a non-obvious resource; no filler beyond that.

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?

There is no output schema, so the description partially compensates by naming the returned fields. Combined with annotations that cover the safety profile and a fully documented single input, this is adequate — but the total absence of disambiguation against three near-identical siblings leaves a genuine gap for correct tool selection.

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?

With one parameter and 100% schema description coverage (including an example value 't' or 'thorswap'), the schema fully documents the input. The description mentions the fields returned, not the input semantics, so it adds nothing beyond the schema — the baseline 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?

States a specific verb and resource ('Returns THORName registration information') and enumerates the returned fields (owner, expiry, registered chain addresses), so the agent knows this is a full-record lookup rather than a single-field one. However, it never distinguishes itself from close siblings like lookup_thorname, get_thorname_owner, or reverse_lookup_thorname, leaving the selection decision ambiguous.

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 when-to-use guidance at all. With three overlapping siblings (lookup_thorname, get_thorname_owner, reverse_lookup_thorname) the description should say which one to pick, but it offers neither conditions nor exclusions.

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