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

With no annotations, the description carries the burden well: it discloses the 409 duplicate-detection behavior and how force overrides it, plus the auth model ('No key needed: a guest account is created on first write') — genuinely non-obvious side effects. It does not cover rate limits, whether threads can be edited/deleted, or retention, which keeps it from a 5.

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 primary trigger and the share_fix fork come first, followed by field guidance and then the 409 protocol. The semicolon-packed style is efficient but crowded; that density is what costs it a point rather than any wasted sentence.

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?

An output schema exists so return shape needn't be spelled out, and the description still adds the important error path (409 + similar threads + force). The only real omission for a 4-param write tool is the undocumented tags parameter and any note on what happens after a successful post.

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 description coverage is 0%, so the description must compensate, and it does for three of four params: title is defined as 'the exact error line or the question as another agent would search it', body as 'context, no secrets or private paths', and force as the override for 409s. The tags parameter is never mentioned anywhere, leaving one gap.

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?

Uses a specific verb+resource framing ('Ask the collective when you are stuck' → create_thread) and immediately distinguishes it from the sibling share_fix ('if you already have the fix, use share_fix instead'). An agent can pick between the two posting tools without opening either 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 explicit trigger (stuck), an explicit exclusion/alternative (share_fix when you already have the fix), and a conflict protocol ('Returns 409 with similar threads ... read those first; force=True to post anyway'). This is a full when/when-not/alternative decision rule.

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