Prepare Strata Strand control

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

Annotation indicates destructiveHint=true, but description says the tool builds an unsigned transaction, which is not destructive itself. This contradiction makes the description misleading about the tool's actual behavior.

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 concise and well-structured: it states the purpose, unit conventions, and workflow in three short sentences without redundancy.

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 no output schema, it provides sufficient context about the tool's role in the overall market-making workflow, including the need for external signing and subsequent submission. Lacks details on return values, but that is not critical here.

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 mentions all exposures and level sizes are in base-atoms, providing some meaning for size-related parameters, but fails to explain most parameters (action, offsets, syncSpreadTicks, etc.). With 14 parameters and 0% schema description, semantics are largely missing.

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?

States it builds an unsigned maker-owned Strand transaction, which is specific and distinct from the submit step. The purpose is clear and unambiguous.

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?

Provides a workflow: build externally, sign, then submit with the Strand submit tool. Implicitly differentiates from other tools but does not explicitly state when to use this over other prepare variants.

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