search_and_fetch

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

With no annotations provided, the description carries the full burden. It discloses caching, blocked domain filtering, a fetch cascade (Firecrawl → Crawl4AI → raw HTTP), and GitHub API handling. It also mentions reranking. It does not mention rate limits, auth needs, or side effects, but given no structural annotations, coverage is strong.

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?

The description is a single, well-front-loaded paragraph of about 80 words. It states the core action first, then details special cases (GitHub, caching, blocked domains, fetch cascade). Every sentence adds value with no redundancy or filler.

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?

Given 9 parameters, no output schema, and moderate complexity, the description covers the process (search, rerank, fetch), caching, domain filtering, and special handling. It also states the return format. It could elaborate on reranking or result list structure, but overall it is reasonably complete for agent invocation.

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 baseline is 3. The description adds significant value beyond schemas: explains 'site' as best-effort with site: operator, 'expand' as local LLM variants with ~3s latency, 'engines' as verbatim with degraded fallback, and 'domain_profile' as named filters (homelab, dev). This extra context elevates the score.

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 the tool's purpose: 'Search the web, rerank results, then fetch the full content of the top result(s).' This verb+resource combination is specific and distinguishes it from siblings like 'search' (plain search) and 'fetch_url' (single URL fetch). The mention of GitHub URL special handling further clarifies its scope.

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 description implies usage for combined search and fetch, but does not explicitly state when to use this tool over alternatives like 'search' followed by 'fetch_url' or 'search_and_summarize'. No exclusions or prerequisites are provided, so usage guidance is implied rather than explicit.

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