transfer_loyalty_tokens

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get calldata' implies a read-only/preparation operation, the description fails to specify the return format (hex string, JSON object), whether validation occurs (balance checks), or any rate limiting concerns.

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, efficient sentence with no redundant words. It front-loads the action ('Get calldata') and maintains focus. However, it may be overly terse given the complexity of blockchain transaction preparation, lacking a second sentence to clarify the output or next steps.

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 generating blockchain transaction data, the description omits crucial context: the nature of the returned calldata, whether it includes gas estimates, and how to use the result. With no output schema and no annotations, the description should compensate by explaining the transaction preparation workflow, which it does not.

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 has 100% description coverage with clear Ethereum address formats and amount specification. The description adds minimal semantic value beyond the schema, merely contextualizing that the transfer occurs 'between wallets', which aligns with the 'to' parameter. Baseline 3 is appropriate given comprehensive schema documentation.

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 specifies the action ('Get calldata'), resource ('loyalty tokens'), and operation ('transfer between wallets'). It implicitly distinguishes from execution-style transfers by specifying 'Get calldata', though it doesn't explicitly contrast with sibling tools like 'mint_loyalty_tokens'.

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, nor does it explain the critical workflow that this generates unsigned transaction data requiring separate signing and submission. No prerequisites or exclusion criteria are mentioned.

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