snowflake_get_query_history

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

Annotations are absent, so the description must carry the full burden. It discloses only the scope (account/user) but says nothing about default behavior, the meaning of 'recent', maximum lookback, or whether any permissions are needed. This is minimal behavioral disclosure for a read tool.

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 a single, efficient sentence that front-loads the verb and resource. There is no fluff or redundancy; every word contributes to the core message.

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?

Although an output schema exists, the description omits crucial operational details: the meaning and effect of 'limit', the recency window, and any constraints like warehouse requirements. It is too sparse for an agent to invoke confidently without additional inference.

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 description does not mention the single 'limit' parameter at all. The agent must guess its meaning from the parameter name alone, which is particularly risky given the default value of 20 is not explained.

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 the action (retrieve) and the resource (recent query execution history), with a specific scope (current account/user). It is not a tautology and is distinct enough from general query tools, though it doesn't explicitly contrast with related siblings like snowflake_get_query_plan.

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 guidance is provided on when to use this tool versus alternatives. With many query-related siblings (e.g., snowflake_get_query_plan, snowflake_get_warehouse_load_history), the agent is left to infer the appropriate context from the vague phrase 'recent query execution history'.

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