create_databricks_database

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

With no annotations, the description bears full burden. It discloses creation of a connection and two auth modes, but does not discuss idempotency, overwrite behavior, or side effects. Sufficient for basic usage but lacks depth for a creation tool.

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 with two short paragraphs, uses numbered list for auth modes, and front-loads the main action. Every sentence adds value without redundancy.

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?

Covers essential aspects: purpose, auth options, and post-creation step. Lacks explicit guidance on mutual exclusivity of password vs. service user fields, but that is inferable from schema. With output schema present, return values need not be explained. Adequate for an agent to operate.

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 coverage is 100%, so baseline is 3. The description adds value by grouping parameters into auth modes (service user vs. password) and indicating that 'service_user_id' comes from 'get_service_users'. This contextualizes parameter relationships beyond the 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 clearly states the tool connects a Databricks workspace to the ALTR platform, with specific verb 'Connect'. It distinguishes from sibling tools like 'create_databricks_job' or 'create_database' by focusing on the connection setup.

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?

Provides clear context on when to use (to connect a Databricks workspace) and recommends a preferred auth mode. Includes a follow-up step to use 'get_databases' to confirm creation. Does not explicitly state when not to use or list alternatives, but the context is adequate.

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