research

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

No annotations provided, so description carries full burden. It discloses core actions (search+scrape), output format (clean markdown, content not links), and cost. Missing failure modes or rate limits, but sufficient for basic use.

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?

Two sentences with no waste. The first sentence front-loads the core functionality and unique value. Every part serves a purpose, including pricing and usage guidance.

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?

The description explains the combined search+scrape behavior, but lacks details on the return structure (e.g., how results are ranked, text format). However, for a tool with no output schema and two simple params, it provides adequate context.

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% with both parameters described. The description reinforces they exist but adds only marginal context (e.g., 'top results', 'clean markdown'). No new constraints or clarifications beyond schema.

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 clearly states 'searches the live web AND reads the top result pages as clean markdown', specifying both the verb and resource. It distinguishes from siblings like web_search and scrape by combining search and scrape in one call.

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 says 'Use to answer questions from fresh sources in a single tool call instead of search-then-scrape round-trips', providing clear when-to-use and an alternative to sibling tools. Also mentions pricing and no signup.

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