search_and_extract

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

No annotations exist, so the description bears full burden. It mentions automatic extraction of 'full content' but omits behavioral traits like potential multiple HTTP requests, rate limiting, or memory/time costs, which are crucial for an agent to understand.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose, though a bit more structure (e.g., listing steps) could improve clarity.

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 lack of output schema and sibling tools (google_search, fetch_url, etc.), the description fails to explain return value structure, highlight limitations, or clarify differentiation, leaving agents to infer too much.

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%; both parameters (query, maxResults) have descriptions. The description adds 'extract result count (default 3)' for maxResults, but this largely mirrors the schema. No additional constraints or usage nuances are provided.

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 performs a search and automatically extracts the full content of the top N results. It distinguishes the combined action but does not explicitly differentiate from siblings like google_search (snippets only) or fetch_url (single 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?

No guidance is provided on when to use this tool versus alternatives, such as for contexts requiring full-page extraction versus snippet-only searches. Prerequisites or exclusions are absent.

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