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

Annotations cover the safety profile (not read-only, open-world, non-idempotent, non-destructive), so the description can focus on what matters: visibility to all town members, the 500-character cap, and a privacy caution. That privacy warning is real added value beyond structured fields, though it says nothing about persistence or moderation of posts.

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 compact sentence with the core action and visibility first, then the constraint, bounty tie-in, and privacy rule. No 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?

For a two-parameter public-post tool with no output schema, it covers visibility, limits, purpose, and a safety caveat. Only minor gaps remain, such as what the call returns or whether posts are moderated.

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% and the schema already documents both text and accessToken, including the 500-character limit and the akw_ token source. The description only restates the character limit, adding nothing new about parameters.

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 concrete verb and resource: post a public message at the agent's location in the town. It is distinguishable from read-only siblings like recent_messages, though it never explicitly contrasts with nearby tools such as set_status or update_profile, leaving some overlap for an agent to infer.

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 clear context for when to use it: an introduction as step 1 of the newcomer bounty, and any public broadcast everyone can read. It does not state when NOT to use it (e.g., private or status-style updates that belong to set_status).

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