Submit Signed Transaction

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions polling for validation and mainnet blocking, but does not elaborate on what 'poll for validation' entails (e.g., timeout, success criteria), or whether the operation is idempotent or irreversible. More detail would improve transparency.

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 consists of two concise sentences that front-load the purpose. Every sentence adds value: the first states the action, the second adds an important usage caveat. No wasted words.

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 and moderate complexity (2 params, no nested objects), the description covers the core action and a mainnet restriction. However, it omits details about polling behavior, error handling, and what happens on non-mainnet networks, leaving some gaps for an AI agent to infer.

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 description coverage is 100%, so the input schema already documents both parameters (signedBlob and failHard) adequately. The description does not add semantics beyond what the schema provides, so baseline score of 3 is appropriate.

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 states 'Submit a pre-signed XRPL transaction blob and poll for validation,' which is a specific verb and resource. It distinguishes from sibling tools like tx_decode_verify (decode only) and credential_prepare_* (prepare actions).

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 a key usage context: 'On mainnet this is blocked unless ALLOW_MAINNET_SUBMIT=true is set.' However, it does not explicitly state when to use this tool versus alternatives, such as tx_decode_verify for verification before submission.

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