Snowflake Create Stage

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the agent knows this is a non-destructive creation operation. The description adds the 'internal' qualifier but omits key behavioral details such as idempotency (if_not_exists default true), required privileges, or what happens on conflicts. This is below the bar for a creation tool with five parameters.

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?

One short sentence, front-loaded, no filler. However, the brevity leaves the definition under-specified for the operation's complexity.

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, but the definition still leaves the agent guessing about optional parameters, default behavior (if_not_exists defaults true), and scoping (database/schema). For a creation tool with five parameters and zero schema descriptions, this is inadequate.

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 compensate. It only implies a stage name and says 'internal', leaving database, schema_name, comment, and if_not_exists completely unexplained. No parameter meaning is added beyond what the schema names already suggest.

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 and resource ('Create an internal named stage') and the object type is clear against siblings like snowflake_drop_stage or snowflake_list_stages. It does not differentiate itself from other create tools beyond resource name, but the combination is unambiguous.

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, prerequisites, or alternatives. The word 'internal' hints at a distinction from external stages, but no such alternative is named or excluded.

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