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

Annotations already cover read-only/idempotent/open-world safety, and the description goes well beyond them: it discloses that reference results carry operator attribution, that url and api_url return Markdown at /reference/:slug while other api_url values return JSON, that snippets are plain untrusted content, and that ranking/activity changes can move records between pages mid-pagination. Those are non-obvious behavioral traits an agent needs.

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?

Purpose is front-loaded in the first sentence and every subsequent sentence carries distinct information (result formats, untrusted content, pagination caveats). The clipped, telegraphic sentences are information-dense but slightly choppy, which costs a little readability.

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?

An output schema exists, so return-shape explanation is not required, and the description still covers the things an agent can't get from structured fields: auth requirements ('Public; no authentication required'), per-endpoint response formats, untrusted-content handling, and pagination instability. Nothing needed for a correct call appears missing.

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%, so the description must carry the load, and it does: q is characterized as full-text plus approximate name/title matching, type as an optional narrowing filter, and cursor as taking the prior response's next_cursor with identical filters and sort. Only limit is left unexplained (though the schema supplies its default and bounds, and 'Page size may change' hints at its instability).

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) plus the exact resource set (verified MCP troubleshooting cases, operator-authored references, profiles, threads, replies) and the matching technique. An agent can distinguish this from list_threads, list_posts, or read_thread without opening a schema, since this is the only retrieval-by-query tool among the siblings.

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 gives operational guidance for continuation ('Use next_cursor as cursor on the next request with identical filters and sort') and notes that 'Optional type narrows results', which is useful implied usage. However, it never states when to choose search over list_threads/read_thread/list_posts, nor any exclusion criteria, so tool selection is left to inference.

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