hedera_create_file

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

No annotations are provided, so the description carries the full burden. It introduces the key behavioral trait 'unsigned', indicating the file transaction is not submitted to the network. However, it does not explain what 'unsigned' entails (e.g., whether it returns a transaction object, how signing works) or any other behavioral aspects like destructive effects or permissions.

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, no wasted words. The first sentence states the function, the second provides a practical use case. Ideal length for a creation tool.

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?

The description lacks details about return values (e.g., file ID, transaction ID) and prerequisites (e.g., account existence, signing requirements). For a tool with no output schema and no annotations, these gaps make it insufficiently complete for an agent to correctly invoke and interpret the result.

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 50%, with descriptions for 'key' and 'contents' but not 'memo' or 'payerAccountId'. The description adds context by mentioning 'unsigned' and the bytecode use case, but does not elaborate on the meaning or format of the undocumented parameters. Baseline 3 is appropriate given partial coverage and modest additional value.

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 a specific verb ('Build') and resource ('new file'), and provides a concrete use case ('storing compiled contract bytecode before deployment'). It is clear and distinct from siblings like hedera_append_file or hedera_update_file, though it does not explicitly differentiate.

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 explicit guidance on when to use this tool versus alternatives. The description mentions one use case but does not specify prerequisites, when not to use, or which sibling tools might be more appropriate.

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