stellar_soroban_deploy

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

No annotations provided, so description carries full burden. It mentions the tool uploads and deploys (write operation) and returns hashes, but does not disclose side effects like fee costs, potential failure modes, or whether it requires account authorization beyond the source account.

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?

Two sentences that efficiently state the action and returned values with no fluff. Front-loaded with main purpose, then the returns.

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 deployment tool, description covers the core functionality and key outputs. Could mention network requirements or fee implications, but complete given schema covers param details and no output schema exists.

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?

Input schema describes all 3 parameters thoroughly (100% coverage). Description adds no extra meaning beyond what 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?

Description clearly states the tool uploads WASM and deploys a Soroban smart contract instance, with specific return values (wasmHash, contractId, transaction hashes). It distinguishes from sibling tools like stellar_soroban_invoke which operate on existing contracts.

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 on when to use this tool versus alternatives like stellar_soroban_invoke or stellar_soroban_simulate. No mention of prerequisites, such as account funding or network setup.

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