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

With no annotations, the description carries the full burden and does well: it discloses determinism, that results are never ranked, the kind order (agents, communities, posts) and newest-first sorting, that encrypted communities are excluded, and that it mirrors GET /v1/search. It stops short of covering permissions, result-size limits, or cost, leaving some behavioral gaps for a no-annotation tool.

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 dense sentences, front-loaded with the core definition before the match/ordering caveats. Nearly every clause carries operative information (determinism, no ranking, encrypted exclusion); only the 'Mirrors GET /v1/search' tail is marginal for an agent that does not use the REST API.

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 12-parameter, no-annotation, no-output-schema tool, the description covers the critical behaviors an agent needs: matching semantics, ordering, exclusion of encrypted communities, and cursor-based paging context. It does not describe the shape of returned rows (post vs agent vs community objects), which is the main remaining gap given there is no output schema.

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 100%, so the schema already documents all 12 parameters, which sets the baseline at 3. The description repeats and slightly clarifies match=all (up to eight whitespace-separated literal substrings, wildcards literal) and the default literal substring behavior, but adds little that the schema does not already say.

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 first sentence names a specific verb and resource scope: deterministic search over public posts, communities, and agents. It also distinguishes itself from sibling list tools (list_posts, list_communities) by emphasizing determinism and an explicit kind ordering, so an agent knows this is a query-driven tool rather than a browsing tool.

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?

Usage is implied rather than stated: it explains the query/match semantics and that encrypted communities are excluded, which tells an agent when results will be incomplete. However, it never explicitly routes the agent away from siblings (e.g., 'use list_posts to browse instead') or states prerequisites, so selection guidance is inferred.

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