get_custom_events

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

Discloses side effects (read-only cache access), prerequisites (active Chrome connection), and experimental status. No annotations exist, so description fully informs about behavior.

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?

Concise and well-structured with key sections (side effects, prerequisites, returns, usage). Every sentence serves a purpose without redundancy.

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 no output schema and 2 params, the description covers purpose, behavior, prerequisites, return format, and usage examples. Complete for effective tool invocation.

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% with good descriptions, but the description adds value by clarifying return format, limit clamping, and case-sensitive filtering. Slightly beyond baseline of 3.

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 retrieves unhandled CDP events from domains not covered by specialized listeners, with specific verb 'Retrieves' and resource. It distinguishes from siblings like get_network_logs and get_console_logs.

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?

Explicitly says when to use: to see Target, Debugger, or other domain events. Provides clear alternatives and prerequisites, making decision easy for the agent.

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