snowflake_describe_function

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

No annotations are provided, so the description carries the full burden. The verb 'describe' appropriately implies a read-only operation, which is fitting. However, the description adds no detail on required permissions, error behavior, or the expected function_signature input format — minimal value beyond what the verb itself conveys.

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 purpose is front-loaded and every word earns its place, though it packs minimal information density.

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 and covers return values, which relieves some burden. The tool is simple (3 params, 1 required), but the critical required parameter's format is unexplained and no routing guidance is given. Adequate but with a notable gap around the function_signature input.

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 should compensate, but it explains none of the three parameters. Most importantly, the required function_signature parameter follows non-obvious Snowflake signature syntax that is left undocumented, leaving the agent without the format needed to invoke the tool correctly.

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 (Describe) and resource (UDF function) and lists exactly what is returned: signature, return type, language, and body. The 'UDF' qualifier implicitly separates it from the sibling snowflake_describe_procedure, though that distinction is not made explicit.

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 vs related siblings such as snowflake_list_functions or snowflake_describe_procedure. No prerequisites, exclusions, or context are provided — the agent must infer the appropriate use case.

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