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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: it depends on Brave Search and performs an AI synthesis step, and it requires BRAVE_SEARCH_KEY. That is real behavioral context, but it omits whether the key is supplied per-call, what the response shape is, and any rate/cost limits.

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 compact sentence with the tool's identity front-loaded and no filler. Slightly repetitive wording ('Web Search Deep: Deep web search') but structurally sound.

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?

No output schema and no annotations mean the description should compensate, but it leaves the ambiguous q/query parameters unexplained and says nothing about return format or failure modes when the Brave key is missing.

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 the schema exposes two near-duplicate optional strings, 'q' and 'query', both undocumented. The description gives no guidance on which one to use or whether they differ, so an agent is left guessing on the single most important input decision.

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 concrete verb+resource (deep web search) and specifies the pipeline: Brave Search results plus DeepSeek AI synthesis. This distinguishes it from the plain x402-web-search sibling by depth/synthesis, though it never names that sibling explicitly.

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 word 'Deep' implies a heavier, research-oriented query as opposed to a quick lookup, so usage is implied rather than stated. It never says when to prefer this over x402-web-search, x402-search, or x402-web-scrape, nor mentions latency/cost tradeoffs.

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