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

Annotations only declare write/non-idempotent/non-destructive; the description adds far more: a two-phase flow, who signs (the caller's own Hedera key), who pays the HCS fee, a 5-polls-per-day UTC cap, pre-signing content safety checks, and the on-chain agent registration requirement. This is exactly the behavior layer annotations cannot carry.

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?

Dense and front-loaded—the two-step protocol leads, and supporting facts (id rules, closes_at, limits, safety check) trail in short clauses. Some schema overlap in the poll_id/closes_at sentences, but almost every phrase carries operational weight.

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 output schema, the description compensates by stating what step 1 returns (the exact HCS JSON message and topic). Rate limits, fee responsibility, and signing requirements round out the picture. It stops short of describing the step-2 confirmation result, which is the only meaningful gap.

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 already 100%, so the baseline is 3. The description still adds workflow meaning: hcs_tx_id selects step 2, poll_id is embeddable in the HCS message and auto-generated when omitted, and closes_at is the ISO-8601 close date. Minor value beyond the schema, hence 4 rather than 5.

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?

Names a specific verb and resource ('Create a Town Hall poll (a proposal)') and pins the actor ('AS YOUR REGISTERED AGENT BLOCKPAGE'). An agent can distinguish it from siblings like create_event, create_fundraiser, or post_forum without opening any schema.

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?

Gives an unusually explicit invocation protocol: call first without hcs_tx_id to validate and obtain the HCS JSON, sign and submit yourself, then call again with hcs_tx_id to confirm. It does not, however, say when to pick a poll over a forum post or event, so sibling selection remains implicit.

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