snowflake_list_streams

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

No annotations are provided, so the description carries the full burden. It only states 'List', implying read-only, but does not disclose any additional behavior such as pagination, filtering semantics, or return format. This is insufficient for a tool with zero annotation coverage.

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 concise sentence that efficiently states the core purpose. It is front-loaded and free of redundancy. However, it is so terse that it sacrifices critical information, but for conciseness itself it earns a high score.

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?

Considering the presence of an output schema and lack of annotations, the description is too sparse. It does not explain the parameters, usage context, or any behavioral traits. An agent would not know how to correctly call this tool beyond inferring it lists streams.

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 description mentions 'in a database or schema', which hints at the database and schema_name parameters, but does not explain the pattern parameter at all. With 0% schema description coverage, the description fails to adequately compensate for undocumented parameters.

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 states a specific action ('List') and resource ('table/view streams') within a scope ('in a database or schema'), giving a clear purpose. However, it does not differentiate from sibling list tools like snowflake_list_tables or snowflake_list_views, so it loses a point for lack of sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when it is more appropriate than other list tools, nor any exclusions or prerequisites.

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