theta_deploy_contract

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

With no annotations provided, the description carries the full burden. It discloses that deployment is irreversible and requires a specific environment variable. This adds significant behavioral context beyond the basic action, though it could mention potential side effects or gas costs.

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 extremely concise with two sentences: the first states the action, the second provides critical warnings. No unnecessary words, and the important information is front-loaded.

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 complexity of deploying a contract and the absence of an output schema, the description adequately covers purpose and key warnings. However, it lacks parameter explanations and does not address optional parameters or expected outcomes, leaving gaps for an AI agent.

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 input schema has 0% description coverage and no parameter descriptions. The tool description does not explain what 'bytecode', 'abi', or 'constructor_args' represent, relying on developer knowledge. This is a notable gap in helping the agent understand parameter purposes.

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 the verb 'Deploy' and resource 'smart contract to Theta mainnet', which distinguishes it from sibling tools like theta_read_contract and theta_get_balance. It is specific 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?

The description mentions a prerequisite (THETA_ALLOW_WRITES=true) and a consequence (irreversible), but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. The usage context is implied but not fully elaborated.

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