query_logs_sql

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

No annotations are provided, so the description carries the full disclosure burden. The '(GET)' marker hints at a read-only, non-destructive call, but there is no mention of required token permissions, rate limits, query cost/timeouts, or result caps — all material for an arbitrary SQL endpoint.

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?

Two short sentences with the operation front-loaded and no padding. The trailing 'Returns the query results' is mildly redundant but acceptable given there is no output schema.

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 an arbitrary SQL execution tool with no output schema and no annotations, the description is under-specified: it omits dialect/dataset scope, result limits, and pagination behavior that an agent needs to call it correctly. Only the zone scope and GET semantics are conveyed.

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% and both parameters (query, zone_id) are documented in the schema, so the baseline is 3. The description adds nothing about SQL dialect, queryable datasets, or time-range requirements that would help an agent construct a valid query string.

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 ('Run a Logs Explorer SQL query') and scopes it to a Cloudflare zone, which implicitly separates it from the account-level sibling query_account_logs_sql. It does not name that sibling explicitly, so an agent must infer the zone/account split.

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 when-to-use or when-not-to-use guidance is given. The description never mentions query_account_logs_sql, retrieve_account_logs, or list_received_logs, so the agent gets no help choosing among the several log-retrieval tools in the sibling set beyond the bare word 'zone'.

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