hedera_delete_topic

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

The description discloses that the tool 'builds (unsigned)' a transaction, implying it does not execute. It also notes 'requires admin key'. With no annotations, this provides basic behavioral context but omits details like irreversibility or error handling.

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 of 10 words effectively conveys the core purpose and key condition (admin key). No redundancy or wasted words.

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's simplicity, the description covers the basic function and a key prerequisite. However, it does not mention side effects (e.g., topic becomes immutable) or error scenarios, leaving some gaps for an 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% parameter description coverage and the description does not explain the parameters individually. 'topicId' is inferable from the tool name, but 'payerAccountId' is unexplained, leaving the agent with insufficient parameter meaning.

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 action (deletion of an HCS topic) and the resource (HCS topic), distinguishing it from sibling tools like create, update, or get topics.

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 that the tool 'requires admin key', indicating a prerequisite. However, it does not specify when to use this tool over alternatives or provide explicit 'when not to use' guidance.

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