create_account

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

Annotations already indicate non-read-only and destructive. The description adds meaningful context by disclosing bandwidth cost from the configured wallet, an external effect not present in annotations. It also notes the requirement for pre-generation, adding behavioral nuance without contradicting annotations.

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?

Three concise sentences with the primary function stated first, followed by essential cost and prerequisite details. No filler or unnecessary repetition.

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 simple activation tool with no output schema, it covers the action, cost, and prerequisite. Minor gaps include lack of mention of the network parameter's behavior and return value, but these are either covered by schema or non-critical.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying that the address parameter must reference an already-generated address, which is a semantic prerequisite not present in the schema description.

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 uses specific verb 'activate' and resource 'new account on the TRON network', clearly distinguishing from sibling generate_account by stating the address must be generated beforehand. This makes the tool's purpose 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?

It provides a clear prerequisite (address must be generated beforehand) and a key cost implication (bandwidth from configured wallet). While it doesn't explicitly name alternative tools or state when not to use, the context strongly implies using generate_account first.

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