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

With annotations present, the description adds useful context by clarifying that the tool returns calldata rather than executing the transfer. However, it does not state whether the caller must sign and send the transaction, what chain is involved, or other operational requirements.

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, front-loaded sentence with no wasted words. It efficiently conveys the core action and output.

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?

Given the tool has no output schema, the description should do more to explain the calldata return format and execution flow. It is sufficient to identify the tool's basic purpose but leaves gaps around how the calldata should be used and whether the caller's wallet is the source.

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 schema already documents all three parameters. The description adds only the phrase 'between wallets', which does not clarify the missing sender parameter or token units beyond what the 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?

The description states a specific verb ('Get') and resource ('calldata') for transferring loyalty tokens between wallets. It is clear what the tool produces, though it does not explicitly distinguish itself from siblings like mint_loyalty_tokens or get_token_balance.

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 explicit guidance on when to use this tool versus alternatives. It implies transferring tokens, but does not mention when not to use it, prerequisites, or related sibling tools.

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