snowflake_query

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

No annotations are provided, so the description must disclose all behavioral traits. It reveals the daemon multiplexing, authentication, and default handling, but does not clarify whether write operations (e.g., INSERT, UPDATE) are allowed or if the tool is read-only. The lack of such disclosure could lead to misuse.

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 paragraph of about 100 words with no fluff. It front-loads the core action and efficiently covers prerequisites, authentication, defaults, and optional parameters. Every sentence contributes meaningful information.

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?

The description adequately covers input parameters and the daemon requirement, but the output format is only minimally described as 'YAML' without details on structure (e.g., list of maps). There is no mention of error handling, timeouts, or limits. Given the lack of an output schema, more detail on return values would be beneficial.

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 coverage is 100%, with each parameter having a brief description. The description adds value by explaining fallback logic for account/user (env vars and settings.json) and contextualizing the optional parameters as per-query overrides. This synthesis aids understanding beyond the schema alone.

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 starts with a specific verb and resource: 'Run SQL against Snowflake and return the result set as YAML.' This clearly distinguishes it from sibling tools, which are either for other Snowflake operations (e.g., snowflake_disconnect, snowflake_sessions) or unrelated functions.

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 explains prerequisites (daemon must be running) and the authentication process, including defaults. It does not explicitly state when not to use this tool or list alternatives, but the context is clear enough for an agent to decide.

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