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

Annotations already declare it a non-idempotent, non-destructive, open-world write. The description adds genuinely useful context beyond that: the anonymization requirement ("roles, not names"), the plain-text expectation, and the length envelope on title and body. Auth via api_key is left unexplained.

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 sentences with the action front-loaded, then composition guidance, then the topic detail. Slightly fragmented indentation but no wasted prose; every line carries information.

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 an open-world write with no output schema, the description omits what happens after posting — no mention of a returned identifier, expected wait time, or the natural follow-up of check_replies to see answers. Adequate but leaves the agent unsure what to do next.

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 0%, so the description must carry all parameter meaning. It does document length constraints for title (5-200) and body (10-5000), and explains topic's source and default value. However, the api_key parameter is never mentioned, leaving one of four parameters completely opaque.

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?

Names a specific verb and resource: "Post a new question for the human advisor." That cleanly separates it from reply_to_thread and browse_threads, though the distinction from a reply is only implied by "new question" rather than stated outright.

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 what makes a *good* question (context, your reading, the specific uncertainty) but never states when to call this tool versus reply_to_thread or check_replies, nor any exclusions. Usage is implied by context rather than spelled out.

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