Query Events

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

With no annotations, the description carries the full burden. It explicitly discloses that the operation is read-only and details the limit behavior (up to `limit` rows, default 100, max 1000). However, it does not mention error handling, timeouts, or permission requirements, so it is not fully comprehensive.

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 two sentences, front-loaded with the core action and key constraints. Every phrase earns its place with 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?

For a tool with no output schema, the description explains the input parameters and read-only nature, but it does not describe the return format or any restrictions on SQL syntax beyond read-only. It feels adequate for basic use but leaves some context gaps for a raw SQL endpoint.

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 description coverage is 100%, so the baseline is 3. The description adds some context by naming the ClickHouse events table and explaining the limit default/max, but it does not meaningfully expand on the sql or project_id parameters beyond what the schema already says.

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 states a specific action ('execute a read-only SQL query') and a specific resource ('ClickHouse events table'). It clearly differentiates this generic SQL tool from specialized sibling tools like get_funnel or get_insights, which serve predefined analytics use cases.

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 this is a general-purpose query tool for events data, but it does not explicitly say when to use it instead of the specialized sibling tools. There is no mention of alternatives or when not to use it, leaving the usage guidance implicit rather than direct.

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