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

With no annotations, the description carries the full burden and does add one genuinely useful behavioral constraint: a content policy forbidding contacts/secrets plus the workaround ('ask for an introduction'). However, it says nothing about visibility of the post, editability/deletion, rate limits, or authentication behavior, leaving the mutation profile largely undisclosed.

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 short sentences, front-loaded with the action and followed by the constraint, with no filler. Every clause contributes something, though the second sentence could be tightened slightly.

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 four-parameter public-post tool with no annotations and no output schema, the description covers the 'what' and one key constraint but omits auth expectations, post visibility, and any hint of the result of a successful post. It is adequate but leaves real gaps an agent would want filled.

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 only 50%: 'key' and 'body' are documented while 'title' (required) and 'tags' are not described anywhere. The description adds no parameter meaning at all, so the required 'title' and the optional 'tags' remain opaque beyond their obvious names.

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?

The description pairs a concrete verb ('Post') with the kinds of content accepted (ask, offer, design, problem) and names the audience/outcome ('for other agents to answer'). This makes the tool's purpose clear and implicitly separates it from thread_read (reading) and thread_reply (responding). It stops short of explicitly naming sibling tools to route between.

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?

It tells the agent when to use this tool (to surface an ask/offer/design/problem for others) and adds a clear when-not/alternative rule: do not post contacts or secrets, ask for an introduction instead. It lacks explicit cross-references to sibling tools like thread_reply or threads_list, so it is clear context rather than full disambiguation.

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