Snowflake Query

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 fully covered. The description adds 'return structured rows with metadata,' but an output schema exists, so this is largely redundant; it provides no information on row-limit enforcement, cost, or timeouts.

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 filler, and the read-only constraint is stated up front. It is efficient but arguably too terse for a tool with two undocumented parameters.

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?

With an output schema covering the return shape and annotations covering safety, those obligations are lifted. The remaining gap is the 0%-documented parameters and the absence of any note on row caps or query constraints, which leaves the definition only minimally complete for a general-purpose SQL executor.

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 neither parameter is explained in the text. The description never says what 'max_rows' does (schema shows only a default of 100) or what SQL dialect/constraints apply to 'query', so it fails to compensate for the documentation gap.

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 (Execute) and resource (SQL SELECT/read-only query on Snowflake), and the 'read-only' qualifier implicitly separates it from the mutating snowflake_execute_dml. However, it names no sibling explicitly, so an agent must still infer which of the ~100 query-adjacent tools (sample_table, export_query_to_stage, warehouse_scale_and_execute) applies.

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 'read-only' framing implies when this tool is appropriate versus the DML sibling, but there is no explicit when-to-use or when-not-to-use statement and no routing to alternatives like snowflake_execute_dml for writes or snowflake_sample_table for sampling. Usage must be inferred.

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