Execute a SELECT query on Snowflake to retrieve data from tables and views, providing direct access to your data for analysis and reporting.
Execute a SELECT query.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | SELECT SQL query to execute |
Changes observed during successful MCP inspections.
v0.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only says 'Execute a SELECT query.' This implies a read-only operation, but it does not explicitly state that no side effects occur, no data is modified, or what happens on invalid queries. The behavioral profile is insufficiently disclosed.
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 extremely concise at 4 words, front-loading the core purpose. While it could be slightly more structured by adding a sentence about return value or constraints, it is not verbose and wastes no words.
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?
Given no output schema and a single parameter, the description is minimally adequate: it states what the tool does. However, it lacks mention of the return format (e.g., result rows), potential limits (e.g., max rows), or error behavior. It is complete enough for a simple tool but could be more informative.
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?
The input schema has 100% coverage with the query parameter description 'SELECT SQL query to execute'. The tool description adds no extra meaning beyond this. Per guidelines, baseline is 3 when coverage is high, and there is no additional 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 clearly states the verb 'Execute' and the resource 'SELECT query', making the tool's function obvious. It is distinct from sibling tools like describe_table or list_tables, which are metadata operations, and append_insight, which is likely a write operation.
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 description provides no guidance on when to use this tool versus alternatives. It does not mention that it is for ad-hoc data retrieval and not for exploring schema or modifying data, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.