Snowflake Read Stream Changes

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 the useful CDC notion of 'unconsumed changes' and the default row count, but omits the behavior that matters most for a stream read — whether reading advances/consumes the offset and what happens on repeated calls.

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 compact sentence that front-loads the verb and the resource. Efficient, though the brevity is partly the reason the semantic gaps above exist.

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, and annotations cover safety. Still, for a CDC stream tool the consumption/invalidation semantics and the meaning of stream_name are left entirely unstated.

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 both parameters. The description only echoes the limit default ('default 10 rows'), which is already in the schema, and says nothing about what stream_name must reference or what limit truncation implies for downstream consumption.

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 (Query) and resource (unconsumed CDC changes in a stream) and adds scoping detail ('unconsumed') that distinguishes it from a plain SELECT. It is clearly separable from siblings like snowflake_list_streams and snowflake_describe_stream, but it doesn't explicitly name those alternatives.

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 when-to-use guidance, no prerequisite (e.g. the stream must exist and be stale/active), and no mention of alternatives such as snowflake_query for arbitrary reads. The agent must infer the trigger condition from the name alone.

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