Submit Strata TWAP transaction

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

Annotations already provide readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=true. The description restates idempotency and adds the 'exactly externally signed' constraint, but it does not explain what the destructive behavior entails, what side effects occur, or any auth/rate-limit considerations.

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, focused sentence with no filler. Key qualifiers are front-loaded and every word adds meaning relative to the tool name.

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?

With 4 required parameters, no output schema, and no reference to the surrounding prepare/challenge/submit flow, the description is not sufficient for an agent to confidently invoke the tool or interpret the result. It lacks prerequisites, expected side effects, and relationship to sibling tools.

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 schema has 0% description coverage and 4 required parameters. The description only weakly maps to signedTransactionBase64 via 'externally signed' and to idempotencyKey via 'idempotently'; it does not explain marketId, twapControlId, or how the parameters relate to the TWAP flow.

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 identifies the action ('Submit') and the resource ('exact externally signed TWAP transaction'), distinguishing it from related tools like strata_twap_prepare and strata_twap_cancel. It adds qualifiers about the transaction being externally signed and idempotent, making the scope specific.

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 about when to use this tool versus alternatives such as strata_execution_submit, strata_order_submit, or other TWAP flow steps. The phrase 'exactly externally signed' implies a prior signing step, but prerequisites and retry conditions are never explicitly described.

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