Snowflake Describe Network Rule

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered externally. The description adds only that it returns mode/type/value-list, which is largely restated by the output schema; it says nothing about qualification requirements or empty-result behavior.

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 economical sentence with no filler. It is front-loaded with the verb, though the parenthetical enum lists make it read more like a return-value spec than an instruction.

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, so return values need not be re-explained, and the description roughly matches that scope. However, for a tool with two undocumented optional qualifiers it should at least indicate how the rule is resolved, which 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% for three parameters (rule_name, database, schema_name), so the description carries the full burden of explaining them. Instead it never mentions the parameters or how the optional database/schema_name qualify the rule name, leaving the agent to guess at scoping.

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 (network rule), and enumerates the attributes returned (mode, type, value list), which distinguishes it from the sibling snowflake_list_network_rules. It is clear what the tool acts on, though it is framed around the returned fields rather than the action itself.

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 when-to-use context is given, and no alternative is named. The agent must infer that this is the per-object counterpart to snowflake_list_network_rules; nothing in the text routes it there or states prerequisites.

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