create_view

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

With no annotations, the description must carry the burden. It includes a CAUTION noting that select_body is executed verbatim as DDL, which is a critical behavioral trait. However, it does not disclose other potential traits like permissions, reversibility, or rate limits.

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 concise (4 sentences) and front-loaded: first sentence states purpose, followed by a caution, then parameter descriptions. No wasted 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?

The tool has 4 required params, no enums, and an output schema (though not shown). The description adequately explains the purpose, the dangerous nature of select_body, and each parameter. It does not mention side effects like overwriting existing views, but for a create tool this is acceptable.

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 schema description coverage is 0%, so the description must add meaning. It defines each parameter: workspace (name/GUID), item (warehouse/endpoint name/GUID), qualified_name (dot-separated, with example), and select_body (the SELECT statement). This fully compensates for the missing schema descriptions.

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 explicitly states 'Create a new SQL view.' This is a specific verb (create) and resource (view), clearly differentiating it from sibling tools like drop_view, update_view, and rename_view.

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 does not provide explicit guidance on when to use this tool vs alternatives (e.g., drop_view, update_view). It lacks when-to-use or when-not-to-use statements, and does not reference siblings.

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