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 transparency burden and largely succeeds. It discloses reranking, the GitHub API path, the Firecrawl→Crawl4AI→raw HTTP cascade, caching, blocked-domain filtering, and the return format. It only omits minor details like rate limits or failure modes.

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?

Four sentences deliver the core purpose, fetch routing logic, caching behavior, filtering, and return value without redundancy. Each sentence adds a distinct behavioral fact, and the primary action is front-loaded.

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 9-parameter tool with no output schema, the description covers the return value (result list + clean markdown) and important runtime behaviors (caching, domain filtering, fetch cascade). The reranking criterion and exact blocked-domain list are unspecified, but the description is sufficient for an agent to invoke it correctly.

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 description coverage is 100%, so the schema already documents all nine parameters. The description adds little parameter-specific meaning beyond mentioning 'top result(s),' which roughly maps to fetch_count. Baseline 3 is appropriate since the schema does the heavy lifting.

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 names a specific composite verb-resource operation: search the web, rerank, then fetch full content of top results. It implicitly distinguishes itself from siblings like search, fetch_url, and search_and_summarize by explicitly covering both search and fetch without mentioning summarization.

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 clearly implies the combined use case—when both search and content retrieval are needed—but never explicitly states when to prefer this tool over search, fetch_url, or search_and_summarize. There are no exclusions or conditional routing hints.

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