Pipes Create Pipe

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that – it doesn't say what auto_ingest changes about behavior (event notifications vs. scheduled ingestion), what happens when the pipe already exists, or that creation has side effects on the account.

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 clean, front-loaded sentence with zero waste, but the brevity comes at the cost of substance; for a six-parameter mutation tool this is under-specified rather than efficiently concise.

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 and annotations exist, so return values and safety needn't be restated. However, given six parameters (two required), a bare copy_statement, and undefined booleans, an agent cannot confidently construct a valid call from this definition alone.

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 only 50%, and the description compensates for none of it. copy_statement (a required parameter) has no description at all, and auto_ingest and if_not_exists – both behaviorally significant flags – are never explained in either the schema or the description.

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 a Snowpipe') and adds the reason ('for continuous ingestion'), which distinguishes it from read-only siblings like pipes_describe_pipe or pipes_get_pipe_status. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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 choose this over alternatives, no prerequisites mentioned (e.g., that a stage and file format must already exist, or that auto_ingest requires a notification integration), and no note about the default if_not_exists=true meaning the call is effectively silent on duplicates.

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