snowflake_list_notification_integrations

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'List' implies a read-only operation, which is useful, but the description does not mention access requirements, scope of listings (e.g., current account only), filtering behavior, rate limits, or any other safety-relevant details. Some behavioral transparency is present, but significant gaps remain.

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?

The description is a single, focused sentence with no filler. It front-loads the core action and resource, and the parenthetical examples add useful scope without bloating the text.

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?

Although the output schema is present and the tool is relatively simple, the description is incomplete for an agent trying to call it correctly. The optional 'pattern' parameter is entirely unexplained, there is no routing guidance among sibling integration-listing tools, and no behavioral context is provided to compensate for the absence of annotations.

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?

The input schema has a single optional 'pattern' parameter with no description, and schema description coverage is 0%. The tool description does not mention the parameter at all, so an agent cannot determine whether the pattern is a SQL LIKE pattern, a regex, how it is applied, or what its default behavior means. This is a major gap because the description must compensate for the undocumented schema.

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 clearly states the operation and resource: listing notification integrations, specifically those configured for alerts, tasks, and cloud messaging such as SNS, PubSub, and Webhooks. It is specific enough that an agent can generally tell it apart from broader sibling tools, though it does not explicitly contrast with snowflake_list_integrations.

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 is provided about when to use this tool versus related alternatives like snowflake_list_integrations, snowflake_list_catalog_integrations, or snowflake_list_external_volumes. The description states what the tool lists, but does not provide context for selecting it among siblings or mention any prerequisites or exclusions.

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