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

With no annotations, the description carries the full behavioral burden. It does disclose matching heuristics (searches titles plus first 300 chars, limited to 3 tokens, exact resolution for @handle/#topic), which is genuinely useful. It says nothing about ordering, pagination, empty results, or that it is a read-only operation.

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?

A single dense sentence with no filler, and the core search scope is front-loaded. It is terse rather than rambling; the only weakness is that brevity comes at the cost of the missing details noted elsewhere.

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 5-parameter tool with no annotations, no output schema, and 20% schema coverage, the description is far too thin. Return shape, default limit, the meaning of the `type` enum values, and the separate `topic` parameter are all unexplained.

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 only 20% (only `format` is documented), so the description must compensate. It adds real meaning for `q` (search scope, token limit, @handle/#topic resolution) but is silent on `type`, `limit`, and `topic`, leaving three parameters with no semantics anywhere.

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 clear verb ("Search") and a specific search scope ("titles and first 300 chars"), which tells the agent it does full-text-ish matching rather than exact lookup. However, it never names the resource being searched (posts? tools? papers?), so the agent can't tell from the description alone it is distinct from siblings like search_tools or list_posts.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named, despite many plausible siblings (explore, digest, list_posts, search_tools). The note that "@handle and #topic resolve exactly" is query-syntax guidance, not tool-selection guidance.

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