snowflake_list_dynamic_tables

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Listing implies a read operation, but the description does not confirm safety (e.g., read-only, non-destructive), nor disclose pagination, limits, ordering, or what 'last refresh status' conveys. For an unannotated tool, this is a meaningful gap.

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 efficient sentence with no filler; the resource and key return fields are front-loaded. Minor deduction only because it ends abruptly without any usage framing, but as a concise statement it is well-structured.

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 structure is covered externally. The description identifies the resource and return fields adequately for a basic listing tool, and all parameters are optional. However, given the huge sibling family and zero annotations, the lack of usage guidance and filtering semantics leaves the description somewhat incomplete.

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 the description mentions none of the three parameters (pattern, database, schema_name). The parameter names and optional defaults are somewhat self-explanatory, but with zero coverage the description should compensate by explaining how filtering/scoping works, and it does not.

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 ('List') and a specific resource ('dynamic tables'), and enumerates the distinguishing fields returned (lag targets, refresh mode, last refresh status). Among a large family of list_* siblings (list_tables, list_views, list_iceberg_tables), naming 'dynamic tables' clearly identifies the target resource.

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 on when to use this tool versus the many sibling listing tools (list_tables, list_views, list_iceberg_tables) or describe_dynamic_table. The only disambiguation comes from the resource name itself, which is inferable; there is no explicit when-to-use / when-not-to-use or alternative routing.

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