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

Goes well beyond the annotations by disclosing that an admin token is required and that it bills per search, plus the important caveat that results are a retrieval proxy for citation rather than any model's answer. It also says the retrieved pages are returned so claims can be verified. What's missing is any note on latency, result volume, or failure behavior for the searches themselves.

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?

Front-loaded with the question it answers and then the differentiator, with no filler paragraphs. A few phrases are persuasive rather than informational ('which is the gap a clean site can still have', 'you are holding the page and are far better placed'), costing some tightness.

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?

With no output schema, the description does the necessary work of saying it returns retrieved pages per query, and it covers cost, auth, and interpretation limits. An agent has enough to call it correctly; only result shape details (per-query grouping, counts) are left implicit.

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 100%, so the baseline is 3, but the description adds real meaning: why `queries` should be natural buyer phrases, that the category enum exists only to build weaker fallback queries, and rough guidance via the schema's max of 4. It doesn't discuss `domain` handling (bare domain vs full URL) because the schema already does.

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?

Frames the operation precisely as live web retrieval for buyer queries that reports which pages answer them and whether this domain is among them. The contrast sentence ('Every other tool here reads the site's own bytes; this reads the market around it') cleanly separates it from the scan/audit siblings without naming each one.

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?

Explicitly instructs to pass `queries` with real buyer phrases, gives two concrete example phrases, and states the category fallback is 'deliberately weak' so the agent knows which path to prefer. It also carves out two negative cases (does not name rival brands, does not report ChatGPT answers) that stop the agent from using it for those jobs.

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