snowflake_cortex_search

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

With no annotations available, the description carries the full burden of disclosing behavior. It only states it is a 'query' which implies a read operation, but does not explicitly confirm read-only behavior, mention any side effects, auth requirements, rate limits, or error conditions. Minimal disclosure leaves the agent uncertain about side effects or restrictions.

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 concise sentence with no filler. It is efficiently structured and front-loaded with the core action. However, it is under-specified given the tool's complexity, but for conciseness, it gets a high score because it wastes no words.

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?

Given the tool has 4 parameters, zero schema description coverage, no annotations, and an existing output schema (which covers return values), the description is grossly inadequate. It fails to explain what a Cortex Search Service index is, how to construct a query, what columns refers to, or what limit does. The agent would be unable to correctly invoke this tool without additional external knowledge.

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%, so the description must compensate by explaining parameters. It provides no information about service_name, query, limit, or columns, leaving the agent unaware of what values are expected or how they affect the search. The description adds no value beyond the raw schema, which is entirely absent of semantic help.

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 specific action ('Query') and resource ('Snowflake Cortex Search Service index'), and adds the scope 'over unstructured text' which differentiates it from other cortex tools like snowflake_cortex_summarize or snowflake_query. It is a concise, unambiguous statement of what the tool does.

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 on when to use this tool versus alternatives such as snowflake_query or other cortex functions. There is no mention of scenarios, prerequisites, or cases where a sibling tool would be more appropriate. The description merely states what it does without context.

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