create-database

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

The description only states the basic action ('Create a new database'), with no disclosure of side effects, idempotency, permission requirements, or error scenarios. Given no annotations, the description fails to convey behavioral traits.

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 short sentence, achieving high conciseness with no wasted words. However, it may be too brief, missing opportunities to add valuable context without becoming verbose.

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 complexity (5 parameters, no output schema, no annotations) and the presence of many sibling tools, the description lacks essential context about how 'database' relates to services, what constraints apply, and typical usage patterns. The description is too minimal to be fully complete.

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 adds no explanations for parameters beyond what the input schema already provides (only name and service have schema descriptions). It does not clarify the format or meaning of owners, tags, or description fields, nor does it compensate for the 60% missing schema coverage.

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 resource (database in OpenMetadata), making the purpose understandable. However, it does not differentiate this tool from other 'create-*' siblings beyond the resource name, lacking specificity about scope or context.

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., update-database), prerequisites (e.g., existence of service), or conditions to avoid misuse. The description assumes the agent knows the workflow.

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