search_and_fetch

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

No annotations provided, so description carries full burden. It fully discloses the fetch cascade (Firecrawl → Crawl4AI → raw HTTP), GitHub API handling, caching, domain filtering, and output format (result list plus fetched markdown). No contradictions.

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 that are front-loaded with the core action. Every sentence adds value: first gives the high-level pipeline, second provides specifics on GitHub, fetch cascade, caching, and output. 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 7 parameters and no output schema, the description effectively covers the tool's process, caching, domain filtering, and output. However, it lacks details on reranking algorithm or sorting order, which are minor gaps for a combined search-fetch tool.

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 some value by explaining 'expand' (local LLM, ~3s latency) and caching behavior, but most parameter details are already in the schema. Does not significantly improve parameter understanding.

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 it searches the web, reranks, and fetches content, with special handling for GitHub URLs. The verb 'search' and resource 'web' are combined with the fetch step, distinguishing it from sibling tools like 'search' or 'fetch_url'.

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 tasks with details on caching and domain filtering, but does not explicitly state when to use this vs. siblings like 'search_and_summarize' or plain 'search'. The context is clear but lacks exclusion guidance.

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