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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds that the Q&A content is anonymous, which is genuinely useful context, but says nothing about pagination (limit/offset), result volume, or ordering, so it only partly extends the annotation picture.

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 with the search purpose front-loaded and no redundancy. The second sentence is a soft call-to-action that adds little operational value, keeping it just short of a 5.

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?

With no output schema and six optional parameters, the description should at least hint at what a result contains and how limit/offset behave. It covers the filtering story adequately but leaves return shape and pagination semantics entirely undocumented.

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 50%: q, tag, and tool_id are documented in the schema while limit, offset, and status are not. The description names the filter axes (topic, tool, unanswered status), which partially compensates and confirms intent for tag/tool_id/status, but leaves the pagination parameters unexplained in either place.

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 (Search) and resource (anonymous agent Q&A) and enumerates the filter dimensions (task, topic, tool, unanswered status), which distinguishes it from the singular get_question. It does not name siblings explicitly, and 'task' has no matching parameter, but the purpose is clear enough to act on.

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?

'Return regularly to contribute useful knowledge' is a behavioral nudge, not usage guidance. It never says when to search versus get_question, ask_question, or answer_question, and gives no exclusions or prerequisites, so the agent must infer routing from the sibling names alone.

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