snowflake_get_database_ddl

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

With no annotations, the description must carry the behavioral burden. It mentions 'exact' DDL, implying a read operation, but does not disclose anything about error conditions, permissions, or the format of the returned DDL. This is minimal coverage for a tool with zero annotation support.

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 one succinct sentence with no filler. It is appropriately front-loaded with the core action and resource, though it lacks depth for a read-only tool.

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?

Given the tool's simplicity (one parameter, output schema present), the description still misses key context: usage differentiation, parameter format, and behavioral expectations. It is not complete enough for an agent to call correctly without additional inference.

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%, so the description must clarify parameter usage. It does not mention 'database_name' at all, leaving the agent to guess whether it expects a plain name or a fully qualified identifier. The description adds no value beyond the schema's bare field name.

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 DATABASE DDL definition'), making the tool's purpose unambiguous. While it doesn't explicitly differentiate from sibling tools like 'get_table_ddl', the resource scope is distinct enough that an agent can infer it.

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 such as 'describe_database' or 'get_table_ddl'. The description only states what it does, not when to choose it or any prerequisites.

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