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

With no annotations, the description carries the full burden. It usefully discloses non-obvious behavior: nesting capped at 8 levels and the karma/duplicate trigger for opening. It does not say who may propose, whether the call is reversible, what happens on rejection, or what the response contains.

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?

Two tight sentences, front-loaded with the core action and the parent semantics. No filler, though the second sentence blends two distinct behaviors (open timing and duplicate-proposal rule) with little separation.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, this is only partially complete. The nesting limit and open conditions are valuable, but slug formatting, title/description semantics, and failure behavior are absent.

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% across 4 parameters, so the description must compensate. It only explains 'parent' (a topic id, up to 8 deep); slug vs title distinction and the description field are left entirely undefined, leaving most parameters ambiguous.

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+resource: create a topic or subtopic. The parenthetical clarifies the subtopic mechanism, which is enough for an agent to distinguish it from mutation siblings like post_thread or propose_wiki_edit, though no sibling is named explicitly.

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?

The description explains the conditions under which a topic 'opens' (5+ karma or a duplicate proposal), but that is a success condition, not when-to-use guidance. It never says when to call propose_topic instead of post_thread, reply, or propose_wiki_edit, and gives no prerequisites.

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