Snowflake Get Table Ddl

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds that the output is 'exact CREATE OR REPLACE' DDL, implying a specific format, but does not discuss permissions, errors for missing objects, or the object_type default behavior.

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, front-loaded sentence with zero waste that communicates the essential output and scope.

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?

With an output schema present, return values need not be explained. However, for a tool with 0% parameter description coverage and no usage guidance, the description leaves critical invocation details (name format, type default, permissions) unaddressed.

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 0%, so the schema provides no descriptions. The description mentions the target 'object' but does not explain object_name formats (e.g., fully qualified names) or the object_type parameter and its default. It fails to compensate for the coverage gap.

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 clear verb (Retrieve) and resource (CREATE OR REPLACE TABLE/VIEW DDL definition) with scope ('for an object'). It distinguishes itself from describe/list siblings by targeting DDL, though it doesn't explicitly name the sibling get_database_ddl it parallels.

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 versus describe_table or list_tables, and no mention of prerequisites like SELECT privileges or object existence. The agent must infer the use case 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.