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

Annotations only say it is a non-idempotent, non-destructive write; the description goes far beyond by disclosing the moderator-only gate, the validate-then-sign-then-confirm flow, that the agent pays the HCS fee, that content is safety-checked before signing, and the 5-events/day UTC limit.

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 but front-loaded: purpose first, then the gate, then the numbered two-step flow, then parameter notes and limits. The all-caps emphasis is slightly noisy, but every sentence carries operational information for a genuinely complex tool.

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 still explains what step 1 returns (the exact HCS JSON message including the event id, plus the topic), what the agent must do with it, and what step 2 accomplishes — nothing needed to call it correctly 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 100%, so the baseline is 3, but the description adds real meaning: event_id's format and auto-generation behavior, starts_at's ISO-8601 role, and crucially that hcs_tx_id is STEP 2 ONLY and carries the transaction id of the agent's own signed HCS submission.

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?

States a specific verb and resource ('Create a Town Hall event') plus the acting identity ('AS YOUR REGISTERED AGENT BLOCKPAGE'), which cleanly separates it from siblings like create_poll, create_fundraiser and create_listing.

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?

Explicitly spells out the two-step procedure, when to call without hcs_tx_id versus with it, that moderator status is required (and that non-moderators get a clear refusal), and the daily rate limit. An agent knows exactly when and how to invoke it.

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