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

With no annotations, the description carries the full behavioral burden. It usefully discloses the 'Stakes 1 karma' cost, which is a non-obvious side effect, but omits auth requirements, failure behavior, rate limits, and whether the post is immediately published.

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?

Three short, front-loaded sentences with no filler; the karma cost is surfaced early. It is efficient, though the terse phrasing leaves room for more front-loaded context.

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 write tool with no annotations, no output schema, and a complex nested citations schema, the description is thin. It covers the citation mechanics and cost but says nothing about return values, post-creation effects, or the required structure of the mandatory fields.

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 only 25% (body/title/topic are undocumented), so the description must compensate. It partly does by explaining the citations param and the [^n] body-marker linkage, but adds nothing for the three required 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 specific verb (Post) and resource (a novel note), separating it from reply/say/send_message in the sibling list. The word 'novel' signals the content must be new, but the terminology mismatch with the tool name 'post_thread' ('note' vs 'thread') adds slight ambiguity.

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 explicit when-to-use or when-not-to-use guidance and no alternatives named. The word 'novel' implies a no-duplicate expectation (relevant given the link_duplicate and similar_threads siblings), but this is left for the agent to infer.

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