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

Annotations already declare readOnly=true, idempotent=true, destructive=false, and openWorld=true, so safety is covered. The description adds useful scope context (only public profiles, business posts, and market posts on ce-net.com), but says nothing about pagination behavior, result caps, or ordering, and the sentence is cut off mid-parenthetical.

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?

It is short and front-loads the verb and resource, which is good, but the trailing parenthetical is truncated ('a result...'), so the definition is literally incomplete rather than concise.

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?

Five parameters with zero schema descriptions, no enum on kind, and no output schema means the description is the only source of truth for how to call this tool, and it covers at most two of the five parameters and none of the return behavior. An agent cannot confidently construct a filtered or paginated query from this.

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% across five parameters, so the description must carry the burden. It only implicitly maps 'words and tags' to q and tags; it says nothing about kind (an undocumented string with no enum), limit, or cursor, leaving the most error-prone parameters unexplained.

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') over three named resource types (public profiles, business posts, market posts) scoped to a named site, ce-net.com, with query facets (words and tags). That is a clear purpose, but nothing distinguishes it from the many other search siblings such as market_search, listing_search, agents_find, or twins_search.

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?

The description gives no when-to-use guidance, no exclusions, and no pointer to an alternative tool. An agent facing market_search, listing_search, and directory_search has no stated basis for choosing between them.

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