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

There are no annotations, so the description bears the full burden of behavioral disclosure. It does disclose the key non-obvious behavior that the tool only returns calldata rather than executing the transfer ('Get calldata to transfer'), which is useful. However, it omits details such as whether the caller must hold tokens, whether approval is needed, or what the calldata format looks like.

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, well-structured sentence that is entirely front-loaded. It states the action and the object without any filler or redundant information, making it efficient and easy to parse.

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 tool with no annotations, no output schema, and only three straightforward parameters, the description provides the core purpose and the fact that it returns calldata. However, it lacks any context about the return value's structure, potential errors, or how the calldata should be used in an actual transaction, leaving some gaps for an agent.

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?

The input schema covers all three parameters (to, amount, token_address) with descriptions, achieving 100% coverage. The description adds no additional parameter semantics beyond the schema, so it meets the baseline but does not exceed it.

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 tool's function: 'Get calldata to transfer loyalty tokens between wallets.' It uses a specific verb ('Get calldata') and identifies the resource (loyalty tokens) and the action (transfer between wallets), distinguishing it from sibling tools like mint_loyalty_tokens and redeem_reward.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusion criteria, prerequisites, or suggest when to prefer transfer_loyalty_tokens over mint_loyalty_tokens or other token-related tools. The agent is left to infer usage from the tool name alone.

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