xflows_build_transaction

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states 'build cross-chain swap transaction' without explaining whether this constructs an unsigned transaction, executes a swap, or requires prior approvals. It does not mention side effects, return format, or any safety-related traits.

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 sentence with no wasted words, making it concise. However, the parenthetical '(section 5)' is vague and may confuse rather than help, slightly diminishing the structural quality.

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 10 parameters, no output schema, and non-trivial behavior (cross-chain swap transaction building), the description is not complete. It lacks any indication of the return value, prerequisites, or behavioral context, making it insufficient for an agent to understand the tool's full role.

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 coverage is 100% with descriptions for every parameter, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides, but it also does not need to compensate for missing schema details.

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?

Description clearly states the tool 'builds a cross-chain swap transaction using XFlows', which is a specific verb and resource. The mention of XFlows helps distinguish it from sibling tools like bridge_create_transaction, but the reference to 'section 5' is cryptic and adds little clarity.

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?

No guidance is provided on when to use this tool vs alternatives such as xflows_get_quote or bridge_create_transaction. No prerequisites, sequencing, or exclusions are mentioned, leaving the agent without context on how to select this tool appropriately.

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