Network List Network Rules

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. Beyond that the description only describes row output fields (quoted_name, quoted_qualified_name), which duplicates the output schema, and says nothing about scoping behavior, result limits, or pagination for an open-world listing tool.

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?

Two short sentences, front-loaded with the core purpose, with no filler. The second sentence on quoted names is somewhat redundant given the tool has an output schema, slightly diluting the focus.

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?

The output schema exists, so return values needn't be explained, yet the description spends its second sentence there while leaving the 'pattern' parameter and the all-null-parameters case unaddressed. For a three-parameter open-world listing tool, that is adequate but with clear gaps.

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 coverage is 67%: database and schema_name carry quoting guidance, but 'pattern' is completely undocumented in both schema and description. The description never mentions pattern or explains its matching semantics (wildcards? case sensitivity?), so it fails to compensate for the coverage gap.

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 ('List network rules') plus a scope ('defined in a database or schema'), which clearly separates it from network_describe_network_rule and network_list_network_policies. It stops short of explicitly naming those siblings as alternatives, but the resource noun alone is distinctive enough for correct selection.

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?

Usage is only implied: the word 'List' plus the database/schema scope hints that you can narrow results, but nothing states when to prefer this over network_describe_network_rule or network_list_network_policies. There is also no guidance on what happens when all three optional parameters are omitted (list everything, or error?).

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