Snowflake Get Database Ddl

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond what annotations provide—it does not mention permissions required, whether the output is a single statement or multiple, or any rate limits. With annotations covering safety, the description's lack of additional behavioral disclosure is acceptable but not enriching.

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, efficient sentence that front-loads the action and resource. It is concise and to the point, though it could be slightly more specific (e.g., 'database definition' instead of 'CREATE DATABASE DDL definition').

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 that the tool has an output schema, the description need not explain return values. However, it is incomplete regarding parameter semantics (0% schema coverage) and lacks usage guidelines. For a simple read tool with one parameter, it should at least describe the expected input, but it does not.

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%, meaning the single parameter 'database_name' is undocumented in the schema. The description does not describe the parameter at all—it does not clarify format, case sensitivity, or whether fully qualified names are needed. For a tool with one required parameter and no schema documentation, the description should compensate but 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?

The description states a specific verb ('Retrieve') and resource ('CREATE DATABASE DDL definition'), which is clear. However, it does not distinguish itself from the sibling tool snowflake_get_table_ddl or others that retrieve DDL, and it slightly mislabels the resource as 'database DDL' rather than just the database definition. The purpose is understandable but lacks 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?

There is no guidance on when to use this tool versus alternatives like snowflake_describe_database or snowflake_get_table_ddl. The description provides no context about when this DDL retrieval is appropriate, leaving the agent to infer usage from the tool name alone.

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