get-search-events-samples

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds non-obvious behavior: there is no server-side event filter, so event_type is applied client-side and offset/limit paginate the unfiltered stream. It also notes this is the only v4 endpoint exposing per-URL exclusion reasons — valuable context beyond the annotations.

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?

Information-dense and front-loaded with the purpose and the key caveat, then the routing rules. Every sentence carries weight, though the two negative routing sentences plus the API-caveat sentence make it slightly longer than strictly necessary.

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?

Covers purpose, the unique return value, a pagination/filtering caveat, and both alternative tools. With no output schema, the description still tells the agent exactly what it gets back (sample URLs plus exclusion reasons). Nothing needed to call it correctly is missing.

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 75% and the schema already documents event_type as a client-side filter, but the description goes further by explaining how that filter interacts with pagination (the unfiltered stream is paginated, then filtered). It adds meaning beyond the schema for the parameters that matter most; host_id/limit/offset are self-evident.

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?

States a specific verb and resource ('Get sample URLs for search events') and immediately names the distinguishing payload ('excluded_url_status'). It explicitly separates itself from get-summary, get-excluded-pages, and get-search-events-history, so an agent can route without opening any schema.

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?

Gives an explicit when-to-use clause plus two explicit when-not-to-use clauses, each naming the correct alternative tool (get-excluded-pages for dropped-page walks, get-search-events-history for counts). This is textbook routing guidance.

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