hedera_submit_message

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

No annotations provided, so description carries full burden. The term 'Build (unsigned)' conflicts with the tool name 'submit_message', causing ambiguity about whether the tool submits the message or just prepares it. No disclosure of network interaction, permissions, or signing requirements.

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 a single sentence with no redundancy. It is concise, though it could be slightly expanded to cover critical details without losing efficiency.

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?

With no annotations, no output schema, and a description that omits parameter guidance, behavioral traits, and return values, the tool is inadequately documented for an agent to use correctly. Essential context like the need for signing is missing.

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 only 33%, and the description adds no parameter-level details beyond the general statement. It does not explain topicId, payerAccountId, or message format, leaving the agent reliant on the sparse 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' and the resource 'message submission to an HCS topic', distinguishing it from sibling tools like hedera_create_topic or hedera_get_topic_info. It specifically targets HCS message submission.

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 guidelines on when to use this tool versus alternatives. It does not mention prerequisites (e.g., need an existing HCS topic) or when not to use it. The 'unsigned' hint is present but not elaborated.

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