snowflake_cortex_analyst_query

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

No annotations are provided, so the description must disclose behavior. It only says 'ask a question', implying a query operation, but doesn't state it's read-only, what happens on execution, whether it requires special permissions, or any limitations. This is insufficient for a tool that likely runs analytical queries.

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 sentence, efficient and to the point. However, it's perhaps too terse, omitting necessary detail, but the wording itself is clear and well-structured.

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's purpose and the presence of an output schema, the description is still incomplete. It doesn't mention prerequisites like needing a semantic model, how to specify it, or any context about the type of questions. An agent would have limited information to call it correctly.

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 should explain the parameters. It does not describe what 'question' should look like or what 'semantic_model_path' refers to beyond the implicit 'using semantic models'. The description adds almost no parameter semantics.

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: ask a natural language analytical question, and specifies the resource: Cortex Analyst semantic models. It differentiates from raw SQL query tools like snowflake_query and general tools like snowflake_cortex_complete by the use of semantic models.

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 on when to use this tool versus alternatives. It doesn't mention snowflake_query or any other tool, nor does it specify conditions like having a semantic model. An agent would have to infer usage context entirely.

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