create-database

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

The description lacks behavioral details such as idempotency, required permissions, or failure conditions (e.g., if the parent service doesn't exist). Since no annotations are provided, the description carries the full burden, but it only gives a high-level purpose.

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 extremely concise: one sentence that immediately conveys the core function. However, it could be structured with more details (e.g., bullet points) while remaining concise.

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 complexity of the tool (5 parameters, many siblings) and no output schema, the description is too minimal. It omits prerequisites (e.g., parent service existence), relationship to siblings, and return value structure, making it incomplete for effective selection.

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 description does not add any information about the parameters beyond the input schema. With only 40% schema description coverage, the description should compensate for undocumented parameters, but it makes no mention of owners, tags, or description format.

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 ('Create') and the resource ('a new database in OpenMetadata'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like create-database-service or create-schema by specifying 'database'.

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 (e.g., if a database already exists, or when to use create-database-service first). The description only states what it does, with no context for appropriate usage.

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