snowflake_list_services

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states a listing action, which implies read-only, but it does not explicitly confirm no side effects, nor does it mention any permissions, rate limits, or output details. The description adds no behavioral context beyond the action itself.

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, direct sentence with no filler. It is appropriately front-loaded with the core purpose and is as concise as possible while remaining informative.

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 tool is simple (no required parameters, no nested objects, and has an output schema), but the description gives minimal context. It omits any guidance on filtering (e.g., pattern semantics, database/schema scoping) or the nature of the returned data. While the output schema covers return format, the lack of parameter explanation leaves the agent underinformed.

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%, meaning the description adds no information about the parameters (pattern, database, schema_name). It does not explain their purpose, format, or relationships. Since the description must compensate for low coverage, this is a major 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 clearly states the action ('List') and the resource ('container services') with a specific scope ('running on SPCS compute pools'). This unambiguously distinguishes it from sibling list tools (e.g., snowflake_list_tables, snowflake_list_compute_pools) without needing further context.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases, or when another listing tool would be preferred. The purpose is implied but no usage context is given.

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