hedera_update_topic

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

The description hints that the tool produces an unsigned transaction but does not explain what that means for behavior (e.g., does it return bytes? Side effects?). No annotations exist, so the description should carry full burden but fails to clarify output or mutation aspects.

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 very short (one sentence) and front-loaded, but it omits critical details. Every word earns its place, but the sentence is too sparse to be fully effective.

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 tool has 3 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain what the tool returns, the role of each parameter, or the transactional nature (build vs execute). Highly incomplete.

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 0%, yet the description only mentions 'memo' implicitly. It does not explain the purpose of 'topicId' (which topic to update) or 'payerAccountId' (who pays). The description adds minimal value beyond the schema.

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 'Build (unsigned) an update' and the resource 'HCS topic memo'. It distinguishes this tool from siblings like hedera_create_topic and hedera_delete_topic by specifying it is for updating a memo.

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 (e.g., hedera_create_topic for new topics, hedera_get_topic_info for reading). No mention of prerequisites, signing, or submission steps.

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