Snowflake Cortex Search

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that this is a semantic search over unstructured text, with no mention of index prerequisites, latency, or how limit/columns affect results. Adequate but thin against a lower annotation-covered bar.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification for a four-parameter tool.

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 explained. However, with four undocumented parameters, no usage guidance, and no behavioral detail beyond the safety hints, the description leaves the agent without enough to invoke the tool confidently.

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 all four parameters, so the schema alone gives no meaning for service_name, query, limit, or columns. The description mentions 'query' and 'index' only implicitly and never explains that service_name identifies the target search service or that limit/columns control result shaping.

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 clear verb (Query) and resource (Snowflake Cortex Search Service index), and the phrase 'over unstructured text' distinguishes it from SQL-oriented siblings like snowflake_query and from the other cortex_* text tools. It stops short of explicitly naming which sibling it replaces, so it lands at 4 rather than 5.

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 guidance is given. With siblings such as snowflake_cortex_complete, snowflake_cortex_extract_answer, and snowflake_query, the agent gets no signal on when semantic index search is the right choice versus an LLM completion or a plain SQL query.

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