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

With no annotations, the description carries full burden and does add real context: it is keyless (no auth), costs $0.025 USDC on Base via x402, and returns an Ed25519-attested result set. Payment model and attestation are meaningful disclosures, but rate limits, error behavior, and result shape are absent.

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-loads the core purpose well, but the pricing is stated twice ($0.025 Base USDC and again in the bracketed x402 line) and the dense notation ('agent-search band', '(?q=)') is cryptic. It is compact but has redundancy and could be tighter.

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 paid, attested search tool with no annotations and no output schema, the description covers cost and verification but omits return format, result count, and failure handling. Adequate but leaves gaps an agent must discover by calling.

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% for the single 'q' parameter, so the baseline is 3. The description's '(?q=)' only restates the query parameter name, adding no syntax or format detail beyond what the schema already documents.

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 and resource ('web search') with a clear purpose qualifier ('for agent grounding'). It distinguishes itself from data-enrichment siblings like lion_scrape or lion_deep_research by being a plain keyless search, though it never names an alternative to route against.

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?

'for agent grounding' implies a use context but gives no when-to-use vs. when-not guidance and never references any of the many sibling research/scrape tools. The agent must infer routing entirely on its own.

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