Queries Cancel Query

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is known. The description adds the confirmation requirement, which is genuinely useful context, but it leaves the mechanics ambiguous (does confirm=false fail the call or silently no-op?) and says nothing about irreversibility or partial cancellation.

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 zero filler; the action and target are front-loaded and the operational caveat follows immediately.

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?

An output schema exists, so return values need not be described, and annotations carry the destructiveness signal. For a destructive mutation with an undefined confirm parameter, though, the description should clarify the confirmation flow and whether cancellation is immediate or graceful.

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 0% across two parameters. The description only covers query_id ('by its Query ID') and gestures at confirm with 'Requires confirmation' without stating that confirm must be set to true or what happens if it is left at the default false.

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 (Cancel), resource (an active running Snowflake query), and identifier (Query ID). This clearly distinguishes it from read-oriented siblings such as queries_query and queries_get_query_history.

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 phrase 'active running query' implies the usage context (cancelling in-flight work), but there is no explicit guidance on when to prefer this over alternatives, no prerequisites, and no statement of when-not to use it.

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