Snowflake Get Query History

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful scope constraint that results are limited to the current account/user, but says nothing about retention windows, ordering, pagination, or result volume, and 'recent' is left undefined.

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?

One short, front-loaded sentence with the scope qualifier placed at the end; nothing is wasted. Its brevity is efficient rather than padded, though the same brevity is what leaves the gaps noted elsewhere.

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-value documentation is not required, and annotations carry the safety profile. What remains missing is the meaning of 'recent', the behavior of the limit parameter, and any routing guidance versus the query-plan and operator-stats siblings.

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% and the single parameter (limit, integer, default 20) is never mentioned in the description, so there is no explanation of what it caps or its default. With a non-empty parameter list and no coverage in either schema or prose, the description fails to compensate.

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 ('Retrieve recent query execution history') and scopes it to 'the current account/user', which is clear enough to distinguish it from record-mutating siblings like snowflake_query or snowflake_execute_dml. It does not, however, differentiate itself from nearby read siblings such as snowflake_get_query_plan or snowflake_get_query_operator_stats, which an agent could easily confuse with it.

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 guidance at all: no mention of what 'recent' covers (time window, row cap), no prerequisites, and no indication of when to prefer this over snowflake_get_query_plan/get_query_operator_stats for a given query. The agent must infer intent entirely from the name.

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