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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: no matching semantics (substring vs full-text), no result limits or ordering, no pagination, no mention of whether search is case-sensitive or whole-word. The only behavioral hint is that matching covers title or body, which is useful but minimal.

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 tight sentence with the scope front-loaded and no filler. It is under-specified rather than bloated, which is the right tradeoff for brevity but leaves gaps 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 tool with no annotations and no output schema, the description should explain what results look like and how many to expect. Neither is covered, so an agent cannot predict the response shape or whether it needs to page or refine the query.

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% and there is one required string parameter, so the description must compensate. 'Words in title or body' does clarify that the query is free-text words matched against post content rather than an ID or filter, but it gives no advice on quoting, multi-word handling, or whether operators are supported.

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 (posts) plus the matching scope (words in title or body), which is more than the bare name 'search' conveys. It does not differentiate itself from sibling read tools like read_feed or read_discussion, so an agent must infer which retrieval path fits.

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?

No indication of when to use this versus read_feed, read_discussion, or read_mentions, all of which could plausibly return posts. There is no statement of prerequisites, exclusions, or expected input format.

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