create-domain

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

No annotations are present, so the description must disclose behavioral traits. It only states 'Create a new domain,' implying a write operation, but does not mention side effects (e.g., overwriting existing domains), required permissions, or whether the operation is idempotent. Fails to provide sufficient transparency.

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, making it concise but overly sparse. While it avoids verbosity, it sacrifices valuable context that could fit without bloat. A slightly more informative description would improve this score.

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?

With no output schema and six parameters (three required), the description lacks completeness. It does not explain return values, error conditions, or how the domain creation ties into the broader system (e.g., relationships with other entities). The context is insufficient for an agent to fully understand the tool's behavior.

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 input schema covers 100% of parameters with descriptions. The description adds no extra meaning beyond what the schema already provides. According to guidelines, high schema coverage sets a baseline of 3, and the description does not exceed that.

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 (domain). It distinguishes this tool from sibling create-* tools like create-chart or create-database, making the purpose clear. However, it lacks additional context about what a domain represents (e.g., in OpenMetadata, domains are logical groupings for data assets).

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 (e.g., when to create a domain vs a glossary term). No prerequisites, exclusions, or context about typical use cases are provided.

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