search_custom_siterestrict

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

No annotations provided, so the description must disclose behavior. It mentions 'Formatted search results' but does not specify the format, error handling, rate limits, or that it requires a Google Custom Search Engine to be configured. The behavioral disclosure is adequate but incomplete for a tool relying on an external API.

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 concise with a single sentence summary followed by structured Args and Returns sections. Every part is informative, and no extraneous text is present. It is well-organized and front-loaded with the core purpose.

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 the complexity (6 parameters, external API dependency) and the presence of an output schema (though not detailed), the description covers parameters and return type. However, it omits necessary context like prerequisites (Custom Search Engine ID), potential errors, or pagination behavior, preventing full completeness. It meets most needs but has clear gaps.

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?

The input schema has 0% description coverage, so the description fully compensates by explaining all six parameters: user_google_email, q, sites, num, start, safe, including defaults and accepted values. This adds significant meaning beyond the bare 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 the tool performs searches restricted to specific sites using Google Custom Search. The verb 'performs' and resource 'restricted to specific sites' define a distinct action, differentiating it from sibling tools like 'search_custom' (which searches without site restriction) and other search tools.

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 does not explicitly state when to use this tool versus alternatives (e.g., 'use this for site-specific searches; use search_custom for general searches'). It implies usage by describing its site-restriction capability, but lacks direct guidance on when not to use it or prerequisites.

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