submit_transaction

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

With no annotations provided, the description carries full disclosure burden. While it states submission occurs via RPC to the Casper network, it lacks critical blockchain-specific context: irreversibility, gas fees, confirmation waiting, synchronous vs asynchronous behavior, or error scenarios.

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?

Single, efficient sentence with zero waste. Front-loaded with the action ('Submit'), followed by object and method. Every phrase earns its place by specifying what, how, and where.

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 the simple 1-parameter schema with complete coverage, the description adequately covers the basic invocation contract. However, for a blockchain mutation tool without output schema or annotations, it omits important operational context like return values or confirmation behavior.

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%, establishing a baseline of 3. The description mentions 'signed transaction' which semantically aligns with the 'signed_deploy_json' parameter, but adds no specific details about JSON format or file path requirements beyond what the schema already provides.

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 provides a specific action (Submit), resource (signed transaction), and target (Casper network via node RPC). It clearly distinguishes from sibling 'build_' tools (which construct transactions) and 'get_' tools (which query data) by focusing on the final submission step.

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 term 'signed transaction' implies prerequisites (you must sign first), suggesting this follows the 'build_' sibling tools. However, there is no explicit guidance on when to use this versus alternatives, or workflow steps mentioned in the text.

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