aedt_create_dataset

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

With no annotations, the description must fully disclose behavioral traits, but it only states the basic creation action. It omits critical behaviors such as overwrite behavior, default units, sorting implications, or whether the dataset replaces an existing one with the same name.

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, which is concise but under-specified for the tool's complexity. It lacks structure and fails to convey essential information, making it insufficient rather than efficient.

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 11 parameters, zero documentation in the schema, and no annotations, the description is far from complete. Even with an output schema available elsewhere, the lack of behavioral and parameter explanation makes it inadequate for reliable agent selection and invocation.

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 description coverage is 0%, yet the description adds no meaning to any of the 11 parameters. It does not explain the roles of name, x, y, z, v, units, sort, or is_project_dataset, leaving the agent to guess their semantics.

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 verb 'Create' and the resource 'AEDT dataset', specifying dimensionality (1D or 3D). This distinguishes it from sibling tools like aedt_import_dataset (import vs create), but could further clarify what constitutes a dataset in the AEDT 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?

The description provides no guidance on when to use this tool versus alternatives. No comparison to aedt_import_dataset or other sibling tools, and no mention of prerequisites or suitability for different scenarios.

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