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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description adds real value by disclosing data provenance: editorial research does not imply the featured business joined, contributions and owner reports are unverified and not purchase intent. Source URLs, dates, support/contradiction fields are also disclosed. It falls short of explaining result ranking or pagination behavior.

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?

At roughly four dense sentences it is not bloated, and each caveat is meaningful. However it front-loads corpus provenance rather than the action, so the reader must reach the end without ever learning how to scope or page the search.

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 needn't be described. But for a zero-required, seven-parameter search tool with no schema descriptions, the description's silence on filters and pagination leaves a material gap an agent cannot fill from structured fields.

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?

All 7 parameters have 0% schema description coverage and the description explains none of them; host, query, problem, industry, geography, limit and cursor are left for the agent to guess. The only faint hint is 'across markets', which loosely gestures at geography, and 'editorial research' which does not map to any parameter.

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 description enumerates what data lives in the graph (editorial research, contributed observations, website-confirmed owner demand) but supplies no operational verb or scoping statement about the search itself. An agent learns the corpus contents, not how this tool differs from browse_owner_demands or scan_review_pain_points. Purpose is inferable from the name and title only.

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 statement of when to call this versus the many sibling read tools (browse_owner_demands, search_businesses, scan_review_pain_points). The one boundary given — 'Private workspaces are never included automatically' — is a scope exclusion, not usage guidance, and no alternatives are named.

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