snowflake_get_table_ddl

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It implies a read-only operation ('Retrieve') but does not mention permission requirements, potential errors for nonexistent objects, or whether it affects state. Given the absence of annotations, more explicit behavioral context would be beneficial.

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 delivers the essential purpose without any redundancy or unnecessary detail. It is front-loaded and immediately understandable.

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?

While an output schema exists to cover return format, the description does not elaborate on usage context such as required permissions or whether the object must be fully qualified. For a simple retrieval tool, the description is adequate but could be enhanced with a brief note on object naming conventions. The brevity leaves some gaps for an agent to handle correctly.

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?

With 0% schema description coverage, the description should compensate by explaining parameter meanings, but it does not. It mentions TABLE/VIEW but does not clarify that object_type can be set to VIEW or that object_name likely requires a fully qualified name. The schema only provides types and defaults, leaving the agent to guess parameter semantics.

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 clearly states the specific verb 'Retrieve' and the exact resource ('CREATE OR REPLACE TABLE/VIEW DDL definition'), making it distinct from sibling tools like snowflake_get_database_ddl or snowflake_describe_table. No ambiguity about what this tool does.

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?

The description does not explicitly state when to use this tool versus alternatives such as snowflake_describe_table or snowflake_get_database_ddl. Situational context is implied by the purpose, but there is no direct guidance on selection criteria or exclusions.

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