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

With no annotations, the description carries the burden and succeeds in disclosing the key behavioral trait: it only prepares an unsigned transaction payload, not a broadcast. It also notes the owner-signature requirement, covering auth needs. Missing details like return format are minor given the clear 'payload' framing.

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?

A single, front-loaded sentence delivers the core function and requirement with zero fluff. Every phrase earns its place, and the key differentiator (unsigned payload) appears immediately.

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?

The tool has 6 parameters, nested objects, no annotations, and no output schema. The description compensates by clarifying the transaction-preparation nature and the owner requirement, but does not describe the exact return payload structure, leaving some ambiguity for an agent needing to sign and submit it.

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%, so the baseline is 3. The description adds grouping by listing social links, website URL, and IPFS avatar CID, which maps to schema parameters, but does not add meaning beyond what the schema already provides for each parameter.

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 states a specific verb ('prepare') and resource ('unsigned transaction payload to update... profile metadata') with concrete fields. It clearly differentiates from siblings like register_domain or transfer_domain by focusing on profile updates built as an unsigned payload.

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?

It provides a prerequisite ('Requires owner wallet signature') and implies the use case, but does not name alternatives or state when not to use it. Sibling differentiation is left to the agent to infer from the tool name and purpose.

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