Snowflake Get Query Operator Stats

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 no further behavioral context such as whether the query must have finished, any retention window for profiling data, or permission requirements. With annotations carrying the safety burden, this is acceptable but thin.

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?

A single, front-loaded sentence with no wasted words. It is appropriately sized for a one-parameter retrieval tool, though it sacrifices some detail in the interest of brevity.

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 explained. For a one-param read tool this is adequate, but the absence of parameter format, prerequisites, and sibling differentiation leaves gaps an agent must resolve by 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% for the single query_id parameter. The description adds the useful constraint that it must be a 'past Query ID' (i.e., a completed query), which is meaning beyond a bare string, but it provides no format details (UUID vs numeric) that an agent would need to supply a valid value.

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 gives a specific verb and resource: 'Retrieve operator-level execution statistics and profiling data for a past Query ID.' An agent can immediately tell this produces granular per-operator profiling. However, it does not distinguish itself from the closely related siblings snowflake_get_query_history and snowflake_get_query_plan, leaving the boundary somewhat ambiguous.

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?

There is no explicit when-to-use guidance and no mention of alternatives. The phrase 'for a past Query ID' weakly implies the query must be completed, but nothing tells the agent when to reach for this versus snowflake_get_query_plan or snowflake_get_query_history.

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