build_clawback_unsigned

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

Discloses key behaviors: returns unsigned JSON + preflight, does not sign, uses testnet by default, and notes prerequisite. With no annotations, description carries full burden and handles it well.

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?

Three compact sentences plus note, front-loaded with purpose, no redundant information.

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?

Covers input requirements, return format, prerequisites, and limitations. Lacks error handling or edge cases but sufficient for a transaction builder.

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?

Description clarifies key parameter roles (account = issuer, holder = target) beyond schema, and notes currency limitation. Schema coverage 80%, description adds value for the two key parameters.

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?

Clearly identifies the tool as assembling an unsigned clawback transaction, specifying the issuer and holder roles, and distinguishes from sibling builders like build_payment_unsigned.

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?

Specifies prerequisite (clawback enabled), limitation (cannot claw native XAH), and behavior (never signs, testnet default). Lacks explicit alternatives but provides clear context for when to use.

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