hedera_create_topic

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Build (unsigned)', which hints at the need for signing, but does not explain the full lifecycle (signing, submission), side effects (topic creation), or requirements for keys. Key behaviors like immutability without adminKey are omitted.

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?

A single sentence front-loads the key concept 'Build (unsigned)' and the purpose. It is concise, but could be slightly longer to include critical behavioral info without becoming verbose.

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 creation tool with 4 parameters, no output schema, and no annotations, the description is too brief. It does not explain the return value (likely an unsigned transaction), the need for subsequent signing/submission, or any prerequisites. The complexity of topic creation (key roles, memo) is under-communicated.

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 schema already describes 3 of 4 parameters (memo, adminKey, submitKey) with useful details. The tool description adds no additional parameter information beyond the schema. The missing payerAccountId parameter has no description in either schema or tool description, leaving a gap.

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 specifies the verb 'Build', the resource 'new HCS topic', and the purpose 'ordered, timestamped messages'. It clearly distinguishes from sibling tools like hedera_update_topic, hedera_delete_topic, and hedera_submit_message.

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 provides no guidance on when to use this tool versus alternatives like hedera_submit_message, hedera_update_topic. It does not mention prerequisites (e.g., need for an existing account) or when not to use it.

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